Vercel MCP now supports Client ID Metadata Documents
Vercel's MCP server now accepts OAuth connections from any MCP client that publishes a Client ID Metadata Document (CIMD) on its own domain, instead of requiring Vercel to review and allowlist each client and its redirect URIs by hand. Users still log in and approve each connection; the consent screen shows the client's name, logo, and metadata hostname, and CIMD clients do not receive the Vercel verified badge.
Why it matters
Builders can connect MCP clients to Vercel without waiting for manual review, but users should check the hostname on the consent screen since unreviewed clients are not verified by Vercel. Apps already registered with Vercel are unchanged.
Who should care
Developers building MCP clients or agents that integrate with Vercel, and teams managing Vercel accounts that authorize MCP connections.
What you can do
If you build an MCP client, publish a Client ID Metadata Document on your domain and use its HTTPS URL as your OAuth client_id to connect to Vercel MCP.