MCP inspector
MCP Inspector is a developer tool for connecting to Model Context Protocol servers to inspect, test, invoke, and diagnose their exposed capabilities.
Spring AI in Action
MCP Inspector is a debugging tool for connecting to Model Context Protocol servers, viewing their capabilities, and invoking their tools.
- How it is used
- Tests MCP servers independently before a full MCP client is configured.
- How deep it goes
- Connects to servers, lists capabilities, and invokes tools, while stopping at surface-level verification.
- Examples
- Uses Java executable JARs, an SSE endpoint, findGamesForPlayerCount, prompts, and a Game List resource.
- What you can do after
- Diagnose/debug with MCP Inspector by connecting to a server, checking exposed capabilities, and running parameterized tools.
AI Agents and Applications
MCP Inspector is an interactive application for connecting to Model Context Protocol servers, inspecting their exposed capabilities, and invoking their tools.
- How it is used
- Validates MCP server connections and tool behavior interactively before integrating servers into agent workflows.
- How deep it goes
- Explains installation, connection settings, status checking, and tool invocation, but stops short of production deployment guidance.
- Examples
- Demonstrates installation with npx and tests a Weather MCP server's get_weather_conditions tool for Penzance, UK.
- What you can do after
- Diagnose MCP server connectivity and invoke exposed tools through a browser interface before application integration.
Read how AI Agents and Applications explains MCP inspector →
AI Agents in Action, Second Edition
MCP Inspector is a developer tool for exploring, invoking, and diagnosing Model Context Protocol servers and their tools.
- How it is used
- Uses a live interface to explore, invoke, and diagnose MCP servers before connecting agents.
- How deep it goes
- Descends from tool-list inspection to calls, return shapes, JSON-RPC traffic, and initialization failures, but not server implementation internals.
- Examples
- Demonstrates a research-sources server, get_research_sources, STDIO, SSE, and an inspection exercise.
- What you can do after
- Diagnose MCP tool failures by inspecting schemas, invoking tools, and locating transport or initialization errors.
Read how AI Agents in Action, Second Edition explains MCP inspector →
Related concepts
- MCP serveruses · An MCP server is software that implements the Model Context Protocol to expose capabilities or information to compatible clients.
- toolkind of · A tool is an instrument or software capability that enables a person or system to perform a task, obtain information, or interact with resources.
- Node.jsuses · Node.js is an open-source JavaScript runtime built on the V8 engine that executes JavaScript outside web browsers and provides APIs for system and network operations.
- mcp clientcontrasts with · An MCP client is a software component that connects a host application to an MCP server to discover and invoke capabilities exposed through the Model Context Protocol.
- http+sse transportuses · HTTP+SSE transport is a communication mechanism that uses HTTP requests and Server-Sent Events for server-to-client streaming between an MCP client and server.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.