{"slug": "latest-mcp-spec-now-supported-in-mcp-handler", "title": "Latest MCP spec now supported in mcp-handler", "summary": "Vercel released mcp-handler@2.0.0 with support for the 2026-07-28 Model Context Protocol specification and MCP TypeScript SDK v2, enabling stateless protocol support without Redis dependency. The update removes deprecated HTTP+SSE transport and requires Node.js 20+ and zod4.", "body_md": "`mcp-handler@2.0.0`\n\nis now available with support for the [2026-07-28 Model Context Protocol specification](https://modelcontextprotocol.io/specification/2026-07-28/changelog) and [MCP TypeScript SDK v2](https://ts.sdk.modelcontextprotocol.io/v2/).\n\nWe originally built [ mcp-handler](https://vercel.com/changelog/mcp-server-support-on-vercel) to make it easier to spin up MCP servers on popular web frameworks including Next, Nuxt, Svelte, and more.\n\nWith the new 2.0 release, the handler now supports:\n\nThe stateless `2026-07-28`\n\nprotocol, served natively, including per-request metadata and server/discover\n\nA stateless compatibility layer for clients using 2025-era Streamable HTTP\n\nBoth protocols with no Redis dependency or session storage\n\nExisting stateless Streamable HTTP clients can continue connecting to the same `/mcp`\n\nendpoint while servers adopt the latest protocol.\n\nInstall the new packages:\n\nCreate a Next.js route handler:\n\nMCP clients can connect to `/api/mcp`\n\n.\n\nGet started with the [Next.js MCP server template](https://vercel.com/templates/template/model-context-protocol-mcp-with-next-js), updated for `mcp-handler`\n\n2.0.\n\nVersion 2 requires Node.js 20 or later and zod4, and replaces `@modelcontextprotocol/sdk`\n\nwith `@modelcontextprotocol/server`\n\n.\n\nTool, prompt, and resource definitions now use the SDK v2 registration APIs and Standard Schema inputs, such as `registerTool`\n\nwith `z.object(...)`\n\n.\n\nThe deprecated HTTP+SSE transport has been removed. Requests to `/sse`\n\nand `/message`\n\nreturn `410 Gone`\n\n. If your clients still depend on that transport, remain on `mcp-handler`\n\n1.x while migrating them to Streamable HTTP.", "url": "https://wpnews.pro/news/latest-mcp-spec-now-supported-in-mcp-handler", "canonical_source": "https://vercel.com/changelog/latest-mcp-spec-now-supported-in-mcp-handler", "published_at": "2026-07-30 00:00:00+00:00", "updated_at": "2026-07-30 16:11:37.415647+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-infrastructure"], "entities": ["Vercel", "mcp-handler", "Model Context Protocol", "MCP TypeScript SDK", "Next.js", "Node.js", "zod4"], "alternates": {"html": "https://wpnews.pro/news/latest-mcp-spec-now-supported-in-mcp-handler", "markdown": "https://wpnews.pro/news/latest-mcp-spec-now-supported-in-mcp-handler.md", "text": "https://wpnews.pro/news/latest-mcp-spec-now-supported-in-mcp-handler.txt", "jsonld": "https://wpnews.pro/news/latest-mcp-spec-now-supported-in-mcp-handler.jsonld"}}