Latest MCP spec now supported in mcp-handler
mcp-handler version 2.0 now supports the latest Model Context Protocol specification and MCP TypeScript SDK v2, with stateless Streamable HTTP compatibility and native MCP protocol support. Node.js 20 or later is required, and the deprecated HTTP+SSE transport has been removed.
is now available with support for the and .mcp-handler@2.0.02026-07-28 Model Context Protocol specificationMCP TypeScript SDK v2
We originally built to make it easier to spin up MCP servers on popular web frameworks including Next, Nuxt, Svelte, and more.mcp-handler
With the new 2.0 release, the handler now supports:
Existing stateless Streamable HTTP clients can continue connecting to the same endpoint while servers adopt the latest protocol./mcp
Install the new packages:
Create a Next.js route handler:
MCP clients can connect to ./api/mcp
Get started with the , updated for 2.0.Next.js MCP server templatemcp-handler
Version 2 requires Node.js 20 or later and zod4, and replaces with .@modelcontextprotocol/sdk@modelcontextprotocol/server
Tool, prompt, and resource definitions now use the SDK v2 registration APIs and Standard Schema inputs, such as with .registerToolz.object(...)
The deprecated HTTP+SSE transport has been removed. Requests to and return . If your clients still depend on that transport, remain on 1.x while migrating them to Streamable HTTP./sse/message410 Gonemcp-handler
The stateless protocol, served natively, including per-request metadata and server/discover
2026-07-28A stateless compatibility layer for clients using 2025-era Streamable HTTP
Both protocols with no Redis dependency or session storage
Before you upgrade
Source: original entry ↗