Run `npx @modelcontextprotocol/inspector <server-command>` to launch the official browser-based MCP debugger, which acts as a full MCP client and lets you list and invoke tools through a web UI.
Imagine you built a small radio that is supposed to broadcast to a specific app, but the app says it cannot hear you. Instead of guessing what went wrong, you want a separate test receiver that listens on the same frequency, shows you exactly what the radio is sending, and lets you press each button one at a time to see what happens. mcp-inspector is that test receiver for MCP servers. You point it at your server, it shows every message in plain view, you click 'list tools' and 'call this tool with these arguments' on a web page, and any error shows up in readable format instead of buried in a host log.
Detailed answer & concept explanation~6 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
3 min: the npx launch command, the inspector as a full MCP client, the five UI panels (traffic, tools with forms, resources, prompts, stderr), the four-step triage for missing from host bugs, and where the inspector falls short (host-specific quirks, CI).
Real products, models, and research that use this idea.
- A junior writes their first FastMCP server in Python, runs the inspector, sees `tools/list` returning empty because the `@app.tool()` decorator was missing, and fixes it in 30 seconds.
- A team debugging a flaky 'resource not found' error uses the inspector to invoke the resource handler with edge-case URIs (trailing slashes, encoded characters) the LLM would never try organically.
- Before publishing a community MCP server to npm, the author runs the inspector against the published package to confirm the install and launch experience works end to end on a clean machine.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy is invoking a tool through the inspector's form better than prompting an LLM to call it?
QWhat is the inspector doing under the hood that a real host also does?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Restarting Claude Desktop repeatedly to debug a missing server. The inspector connects directly to the server process and surfaces the actual error in seconds, without needing any host running.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.