Vercel MCP now supports the 2026-07-28 MCP specification

Vercel lets clients using two generations of the Model Context Protocol connect through the same MCP endpoint. Its July 31 announcement says clients built for the 2025 protocol continue working, while clients that understand the July 28, 2026 specification automatically use its newer request and authorization behavior.

The migration happens without changing the server connection setup. Existing clients retain their supported behavior, and compatible newer clients can adopt the updated protocol without requiring a separate endpoint.

“Vercel MCP now supports the 2026-07-28 MCP specification, giving newer clients a stateless request model and updated authorization behavior without any change on the client side.”

“Clients built for the 2025 protocol keep working exactly as before, and clients that understand the new specification pick it up automatically.”

“Both protocol versions are served from the same endpoint through the official MCP SDK v2 and mcp-handler 2.x, which added support for the latest spec , so a single connection handles either protocol.”