MCP Inspector as MCP Server

MCP Inspector as MCP Server

Enables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.

Category
Visit Server

README

MCP Inspector as MCP Server

A lean MCP server that enables LLMs to inspect and test other MCP servers. This is a self-contained implementation that uses the MCP SDK directly, without shelling out to external CLIs.

Features

  • Direct SDK integration: Uses @modelcontextprotocol/sdk directly for both server and client operations
  • All transport types: Supports stdio, SSE, and HTTP (streamable) transports
  • Minimal footprint: Single dependency (@modelcontextprotocol/sdk)
  • Full MCP inspection: List tools, call tools, list resources, read resources, list prompts, get prompts
  • Session management: Persistent connections with automatic garbage collection
  • Event buffering: Capture notifications, traffic, and errors for debugging

Installation

npm install
npm run build

Usage

As an MCP Server

Add to your MCP config. While there are slight variances between different harnesses, the general format is the same:

{
  "mcpServers": {
    "mcp-inspector": {
      "command": "node",
      "args": ["/path/to/mcp-inspector-as-mcp-server/dist/server.js"]
    }
  }
}

Available Tools

Session Management (NEW in v2.0)

Tool Description
insp_connect Establish a persistent connection to an MCP server. Returns a session_id.
insp_disconnect Close a persistent session and release resources.
insp_list_sessions List all active sessions with their status and idle time.
insp_read_events Read buffered events (notifications, traffic, errors) from a session.

Inspection Tools

Tool Description
insp_tools_list List all tools exposed by an MCP server
insp_tools_call Call a tool on an MCP server
insp_resources_list List all resources exposed by an MCP server
insp_resources_read Read a specific resource
insp_resources_templates List resource templates
insp_prompts_list List all prompts
insp_prompts_get Get a specific prompt

Connection Parameters

All tools accept the following connection parameters:

For stdio transport (local commands):

  • command: Command to run (e.g., "node", "python")
  • args: Array of arguments (e.g., ["path/to/server.js"])

For SSE/HTTP transport (remote servers):

  • url: Server URL (e.g., "http://localhost:3000/sse")
  • headers: Optional HTTP headers object

Common:

  • transport: Force transport type ("stdio", "sse", or "http"). Auto-detected if not specified.
  • session_id: (Optional) Use an existing persistent session instead of creating an ephemeral connection.

Session Workflow

For debugging stateful server behavior, use persistent sessions:

1. insp_connect → returns session_id
2. insp_tools_list (with session_id) → uses persistent connection
3. insp_tools_call (with session_id) → state is preserved
4. insp_read_events (with session_id) → see notifications
5. insp_disconnect (with session_id) → cleanup

Sessions auto-close after 30 minutes of inactivity.

Examples

List tools from a local MCP server (ephemeral):

{
  "command": "node",
  "args": ["/path/to/some-mcp-server/dist/server.js"]
}

Create a persistent session:

{
  "command": "node",
  "args": ["/path/to/some-mcp-server/dist/server.js"]
}
// Returns: { "session_id": "sess_abc123", "server_info": {...} }

Call a tool using a session:

{
  "session_id": "sess_abc123",
  "tool_name": "search",
  "tool_args": {"query": "hello"}
}

Architecture

src/
├── server.ts     # MCP server exposing inspector tools
├── client.ts     # Client wrapper (hybrid stateless/session mode)
├── transport.ts  # Transport factory (stdio, SSE, HTTP)
├── session.ts    # SessionRegistry with GC (30-min TTL)
└── events.ts     # EventBuffer (ring buffer for notifications)

Why This Exists

The original MCP Inspector is a web-based UI + CLI combo spread across multiple projects. This consolidates the core functionality into a single, lean MCP server that an LLM can use to:

  1. Develop and debug MCP servers iteratively
  2. Test MCP server functionality without leaving the conversation
  3. Explore what tools/resources/prompts an MCP server exposes
  4. Debug stateful behavior with persistent sessions

Changelog

v2.0.0

  • Added session management (insp_connect, insp_disconnect, insp_list_sessions)
  • Added event buffering (insp_read_events)
  • All inspection tools now support optional session_id for persistent connections
  • Added automatic garbage collection (30-minute TTL for idle sessions)
  • Backward compatible: omit session_id for original ephemeral behavior

v1.0.0

  • Initial release with ephemeral connections

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured