Vercel MCP serves the 2026-07-28 revision in production three days after release
Vercel's first-party MCP server at mcp.vercel.com now supports the stateless 2026-07-28 specification, serving newer clients the stateless request model while 2025-era clients keep working from the same endpoint, via MCP SDK v2 and mcp-handler 2.0.
Vercel announced on July 31 that Vercel MCP, its first-party hosted MCP server, supports the 2026-07-28 specification in production. Clients built for the 2025 protocol keep working exactly as before, and clients that understand the new revision pick up the stateless request model automatically; both protocol versions are served from the same mcp.vercel.com endpoint through the official MCP SDK v2 and mcp-handler 2.x.
The mcp-handler 2.0.0 release a day earlier brought the same dual-protocol behavior to servers built on the framework: native 2026-07-28 support including per-request metadata and server/discover, a stateless compatibility layer for 2025-era Streamable HTTP clients, and no Redis or session-storage dependency. The handler also removed the deprecated HTTP+SSE transport, with requests to /sse and /message returning 410 Gone.
The adoption tracker records this as a verified support record for MCP 2026-07-28.
Related servers and clients
- Vercel MCP - server
Related spec revisions
- MCP 2026-07-28 - current
Related publishers
How was this verified, and what are the sources?
Published · last verified · confidence 0.95.
- Vercel changelog (2026-07-31) - "Vercel MCP now supports the 2026-07-28 MCP specification"; both protocol versions served from the same endpoint - accessed
- Vercel changelog (2026-07-30) - mcp-handler 2.0.0 released with native 2026-07-28 support, a 2025-era compatibility layer, and no Redis or session-storage dependency; deprecated HTTP+SSE removed with /sse returning 410 Gone - accessed