MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

MCP Inspector 2.2.0 moves to TypeScript SDK 2.0.0 stable and adds a v1 to v2 migration guide

MCP Inspector released 2.2.0 on 2026-08-12, upgrading from TypeScript SDK 2.0.0-beta.5 to the stable 2.0.0 packages, adding a v1 to v2 migration guide, fixing the MCP Apps sandbox proxy so it ships its static assets, and forwarding the negotiated Mcp-Protocol-Version header through the remote proxy. The release also publishes a six-month roadmap running to February 2027.

MCP Inspector, the official debugging tool for MCP servers, released 2.2.0 on 2026-08-12. The release moves the tool off the TypeScript SDK beta line, upgrading from 2.0.0-beta.5 to the stable 2.0.0 packages (#1989), and adds a documented v1 to v2 migration guide for Inspector users (#1960).

Two fixes matter for protocol fidelity: the remote proxy now forwards the negotiated Mcp-Protocol-Version header instead of dropping it (#1963), and the MCP Apps sandbox proxy works again because the clients/web/static assets are shipped in the published package (#1934). The Docker image also publishes on loopback by default and makes a mounted state directory writable (#1974), narrowing its default network exposure.

The release lands five weeks after 2.1.0 added SEP-2243 header mirroring and includes a published six-month roadmap covering August 2026 through February 2027 (#1981).

Related spec revisions

How was this verified, and what are the sources?

Published · last verified · confidence 1.00.

  1. MCP Inspector 2.2.0 release notes (published 2026-08-12T16:46Z) - lists the TypeScript SDK upgrade from 2.0.0-beta.5 to 2.0.0 (#1989), the v1 to v2 migration guide (#1960), shipping clients/web/static so the MCP Apps sandbox proxy loads (#1934), forwarding the negotiated Mcp-Protocol-Version through the remote proxy (#1963), Docker publishing on loopback by default (#1974), and the six-month roadmap (#1981) - accessed

← All news