Vercel: Runs MCP servers as Vercel Functions on Fluid compute through the open-source mcp-handler package, and operates its own OAuth-protected Vercel MCP at mcp.vercel.com. Remote transport: Streamable HTTP only. Price read 4 November 2026: Vercel MCP is available on all plans.
mcp-handler does not run an authorization server or issue tokens.
Does not offer a public MCP registry or directory.
Dated facts
The deploy guide installs mcp-handler@2.1.1 with @modelcontextprotocol/server@2 and zod@4, and needs Node.js 20 or later. (vercel.com, read 4 November 2026)
mcp-handler v2 removes the legacy HTTP+SSE transport and the Redis configuration; clients connect over Streamable HTTP at a framework route such as /api/mcp. (vercel.com, read 4 November 2026)
withMcpAuth wraps a handler with token verification and returns 401 without a valid token and 403 when a scope is missing; the package does not issue tokens or run an authorization server. (vercel.com, read 4 November 2026)
protectedResourceHandler serves /.well-known/oauth-protected-resource metadata pointing at an external authorization server. (vercel.com, read 4 November 2026)
Vercel MCP is a remote server with OAuth at https://mcp.vercel.com, available on all plans. (vercel.com, read 4 November 2026)
Since 2 Nov 2026 any MCP client can connect to Vercel MCP with a Client ID Metadata Document instead of a prior review; the consent screen shows the metadata hostname. (vercel.com, dated 2 November 2026, read 4 November 2026)
The supported-clients list names 14 clients, including Claude Code, ChatGPT, Codex CLI, Cursor, VS Code with Copilot, Devin, Goose, Windsurf, Gemini CLI, OpenCode and Pi. (vercel.com, read 4 November 2026)
Vercel publishes its server in the official registry as com.vercel/vercel-mcp at https://mcp.vercel.com. (registry.modelcontextprotocol.io, read 4 November 2026)