VercelEngineering PostOfficial Source

Vercel MCP now supports Client ID Metadata Documents

Vercel MCP now accepts clients using domain-hosted Client ID Metadata Documents, removing Vercel's prior allowlist review. Approval still depends on trusting the metadata hostname.

Vercel · Nov 2, 2026

Open Source Open Markdown Open JSON

Source Summary

Any MCP client can request a Vercel connection using a **Client ID Metadata Document (CIMD)**: a JSON file on the client's domain, referenced by its HTTPS URL as the OAuth client_id. Users still log in and approve each connection.

Practical Implication

Builders integrating Vercel MCP can publish CIMD metadata instead of waiting for Vercel to review and allowlist the client and redirect URIs. At approval, check the hostname serving the document; these clients lack Vercel's verified badge.

Agent-Ready Context

Any MCP client can request a Vercel connection using a **Client ID Metadata Document (CIMD)**: a JSON file on the client's domain, referenced by its HTTPS URL as the OAuth client_id. Users still log in and approve each connection.

Builders integrating Vercel MCP can publish CIMD metadata instead of waiting for Vercel to review and allowlist the client and redirect URIs. At approval, check the hostname serving the document; these clients lack Vercel's verified badge.

Previously registered apps are unchanged. The material says the MCP authorization spec recommends CIMD over Dynamic Client Registration, but does not describe client-side security checks beyond the consent screen.

Connected Context · Feed7 Judgment

CIMD lets MCP clients request a Vercel connection without prior app allowlisting, while leaving login and per-connection user approval in place. It lowers client registration friction but makes the metadata document’s hostname a relevant approval signal; the brief does not establish further client-side checks.

A2M: Trace-Optimized Agent Hijacking in the MCP EcosystemBoth make MCP metadata relevant to security: this change introduces a client metadata document users should inspect, while A2M describes malicious tool metadata influencing agent behavior. The latter does not establish a CIMD-specific attack.Latest MCP spec now supported in mcp-handlerBoth concern evolving MCP authorization and protocol integration: CIMD changes how clients identify themselves to Vercel, while the handler update changes server protocol compatibility. They address distinct layers of integration.

Context Map

contextcodingsecurity#mcp#tool-use

Uncertainty

Previously registered apps are unchanged. The material says the MCP authorization spec recommends CIMD over Dynamic Client Registration, but does not describe client-side security checks beyond the consent screen.