ToolsThe story, in brief

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

Vercel MCP upgrades to 2026 spec with zero breaking changes — stateless requests and new auth, but your setup stays the same.

Paper-cut illustration of a coral software window opening into a three-dimensional drafting space.
New tools for building and creating with AI.AI illustration by KeyNews
The KeyNews take

Why it matters

A widely-used AI tool integration (MCP servers) ships a backward-compatible protocol upgrade. Practitioners using Vercel MCP or building MCP clients need to know this exists; no action required, but new capabilities are available.

The key facts

14 to know
  1. 2026-07-28 MCP specification released

  2. Stateless request model introduced

  3. Updated authorization behavior

  4. Full backward compatibility with 2025 protocol clients

  5. Single endpoint serves both protocol versions via MCP SDK v2 and 2.x

  6. No setup changes required

  7. npx add-mcp https://mcp.vercel.com remains the same command

  8. Vercel MCP supports 2026-07-28 MCP specification

  9. Stateless request model in new spec

  10. Backward compatible with 2025 protocol clients

  11. Single endpoint serves both protocol versions

  12. Official MCP SDK v2.x required

  13. Zero setup change for existing deployments

  14. Automatic protocol detection for new clients

Go to the source

Vercel Blogvercel.com

Publisher excerpt: 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.Vercel MCP Clients built for the 2025 protocol keep working exactly as before, and clients that understand the new specification…
Read original report
Back to today's editionMore tools news

Keep reading

Related stories

More from Tools