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

DevFeed: [Vercel MCP now supports the 2026-07-28 MCP specification](<https://devfeed.tech/articles/vercel-mcp-now-supports-the-2026-07-28-mcp-specification-1157.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-mcp-now-supports-the-2026-07-28-mcp-specification>)

Author: Josh Souphanthong

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

Content type: release

Language: en

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

Topics: [MCP](<https://devfeed.tech/topics/mcp.md>), [Model Context Protocol](<https://devfeed.tech/topics/model-context-protocol.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [client](<https://devfeed.tech/topics/client.md>), [Server](<https://devfeed.tech/topics/server.md>), [changelog](<https://devfeed.tech/topics/changelog.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [changelog](<https://devfeed.tech/tags/changelog.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [server](<https://devfeed.tech/tags/server.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel MCP supports the 2026-07-28 MCP specification, adding a stateless request model and updated authorization behavior. Existing 2025-protocol clients continue to work, while compatible newer clients adopt the specification automatically through the same endpoint and connection.

## Source excerpt

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. Nothing about setup changes. Add the server the same way you always have. npx add-mcp https://mcp.vercel.com You can also run vercel mcp. See the Vercel MCP documentation to connect your client. For the full list of protocol changes, read the 2026 specification changelog and the authorization announcement. Read more