Vercel MCP now supports the 2026-07-28 MCP specification
TL;DR · AI 摘要
Vercel MCP现已支持2026-07-28规范，实现无状态请求模型和自动协议升级。
核心要点
- 2026-07-28规范引入无状态请求模型和更新授权机制
- 2025协议客户端无需修改即可继续使用
- 通过v2 SDK和mcp-handler 2.x统一支持双协议版本
结构提纲
按章节快速跳转。
- §核心更新
宣布支持2026-07-28 MCP规范，引入无状态请求模型
2025协议客户端保持原有行为不变
- ›实现方式
通过SDK v2和mcp-handler 2.x统一处理双协议版本
- ·部署方式
服务器添加方式与原有流程完全一致
思维导图
用一张图看清主题之间的关系。
查看大纲文本（无障碍 / 无 JS 友好）
- Vercel MCP协议更新
- 2026-07-28新特性
- 无状态请求模型
- 更新授权机制
- 兼容性方案
- 2025协议客户端兼容
- 自动协议识别
- 部署方式
- 统一端点处理
- v2 SDK支持
金句 / Highlights
值得收藏与分享的关键句。
新规范实现无状态请求模型和更新授权行为，无需客户端修改
2025协议客户端与2026规范客户端可共存于同一端点
部署命令保持不变：npx add-mcp https://mcp.vercel.com
Vercel MCP now supports the 2026-07-28 MCP specification - Vercel
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 .