Vercel MCP now supports the 2026-07-28 MCP specification
Vercel MCP now serves the 2026-07-28 and 2025 protocols from one endpoint, letting newer clients adopt stateless requests and revised authorization without breaking older setups.
Vercel MCP supports the **2026-07-28 specification**, including a stateless request model and updated authorization behavior. Clients that understand it adopt it automatically, while **2025 protocol** clients continue unchanged.
Keep the existing endpoint and setup. A single connection handles both versions through **MCP SDK v2** and mcp-handler 2.x, reducing the need for version-specific server configuration.
Vercel MCP supports the **2026-07-28 specification**, including a stateless request model and updated authorization behavior. Clients that understand it adopt it automatically, while **2025 protocol** clients continue unchanged. Keep the existing endpoint and setup. A single connection handles both versions through **MCP SDK v2** and mcp-handler 2.x, reducing the need for version-specific server configuration. The material names the protocol changes but does not detail their operational consequences. Builders should review the specification changelog before relying on new authorization or stateless behavior in custom clients.
This confirms a compatibility bridge rather than a forced protocol cutover: capable clients gain stateless requests and revised authorization while 2025 clients keep using the same endpoint. It narrows server-side migration complexity, but does not remove client and runtime prerequisites or explain the security and lifecycle consequences of the new behavior, so custom integrations still need specification-level review.