MCP ↔ wire ↔ Studio data flow

Studio and the MCP server are two different clients of the same inspection surface — the /_nwire/* endpoints exposed by every running wire. Studio talks to the wire over HTTP from a browser; MCP talks to it over HTTP from a stdio bridge that Claude drives. Both flows read identical JSON, so an answer Claude returns will match what you see in Studio.

What this guarantees:

• Both clients see the same scanner output (.nwire/manifest.json served live), so Claude's understanding stays consistent with what a human sees in Studio.
• The wire is the only authoritative source — neither MCP nor Studio caches manifests across runs.
• Studio's Live page and the MCP recent_telemetry tool share the same ring buffer.

See also

• MCP from Claude
• Debugging with trace
• Telemetry kinds