# Latest MCP spec now supported in mcp-handler

DevFeed: [Latest MCP spec now supported in mcp-handler](<https://devfeed.tech/articles/latest-mcp-spec-now-supported-in-mcp-handler-996.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/latest-mcp-spec-now-supported-in-mcp-handler>)

Author: Andrew Qu

Published: 2026-07-30T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [MCP Server](<https://devfeed.tech/topics/mcp-server.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Nuxt.js](<https://devfeed.tech/topics/nuxt.md>), [Redis](<https://devfeed.tech/topics/redis.md>), [Svelte](<https://devfeed.tech/topics/svelte.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [model-context-protocol](<https://devfeed.tech/tags/model-context-protocol.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [redis](<https://devfeed.tech/tags/redis.md>), [release](<https://devfeed.tech/tags/release.md>), [svelte](<https://devfeed.tech/tags/svelte.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

## AI overview

mcp-handler 2.0.0 supports the 2026-07-28 Model Context Protocol specification and MCP TypeScript SDK v2. It adds native stateless protocol support, compatibility with 2025-era Streamable HTTP clients, and operation without Redis or session storage.

## Source excerpt

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