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

Source: [Vercel](https://vercel.com/changelog/vercel-mcp-now-supports-the-2026-07-28-mcp-specification)  
Feed7 permalink: https://feed7.dev/p/vercel-mcp-now-supports-the-2026-07-28-mcp-specification-0nbflb7  
Published: 2026-07-31T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

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.

## Source Summary

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.

## Practical Implication

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.

## Agent-Ready Context

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.

## Connected Context

Feed7 judgment across 318 accumulated Signals:

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.

- [Latest MCP spec now supported in mcp-handler](https://feed7.dev/p/latest-mcp-spec-now-supported-in-mcp-handler-1kkt3s0) — The handler release supplies the concrete migration boundary omitted here: SDK v2, Node.js 20, Standard Schema, and zod 4 become prerequisites, and HTTP+SSE clients must change transport even though 2025 Streamable HTTP remains compatible.
- [Agent Runs now available in the Vercel MCP and CLI](https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04) — Agent Runs is a concrete Vercel MCP capability; dual-version support lets newer and existing compatible clients access such tools through one endpoint while they migrate on separate schedules.

## Context Map

- Layer: context
- Domains: coding
- Topics: mcp, context-engineering

## Uncertainty

- 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.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.