Latest MCP spec now supported in mcp-handler

mcp-handler@2.0.0 is now available with support for the 2026-07-28 Model Context Protocol specification and MCP TypeScript SDK v2. The release comes from the Vercel blog and targets the same library the team originally built to simplify spinning up MCP servers on popular web frameworks, including Next, Nuxt, and Svelte-related stacks.

Under the hood, the 2.0.0 cut aligns the handler with the 2026-07-28 MCP specification and the MCP TypeScript SDK v2 surface. That means request handling, protocol negotiation, and server wiring sit on the current spec and SDK rather than an earlier protocol revision. For framework-hosted servers, the library remains the adapter between the web runtime and the MCP session model instead of requiring each app to reimplement protocol plumbing.

For engineers and builders, the practical win is lower friction when standing up MCP servers inside existing Next, Nuxt, or Svelte-family apps. Teams already on mcp-handler can move to 2.0.0 to pick up the new specification and TypeScript SDK v2 without rebuilding their server layer from scratch. That keeps tool and context servers closer to the app code that owns auth, routing, and deploy config.

In the broader MCP ecosystem, host frameworks and SDKs are the choke points: if handlers lag the spec, production servers stay stuck on older protocol versions even when clients and tools move forward. Shipping mcp-handler@2.0.0 with 2026-07-28 support and MCP TypeScript SDK v2 reduces that lag for Vercel’s web-framework audience and keeps those stacks viable as MCP clients and servers standardize on the newer contract.

If you already run MCP servers through mcp-handler, plan an upgrade path to 2.0.0 and verify behavior against the 2026-07-28 specification and TypeScript SDK v2 in your Next, Nuxt, or Svelte-side setup. Watch for any follow-on handler releases that tighten framework-specific adapters as more of the stack settles on the same protocol revision.