Vercel MCP opens to all clients via Client ID Metadata Documents, ending allowlist friction
steren · x · 2026-11-10
Vercel MCP now supports Client ID Metadata Documents (CIMD), so any MCP client can request access without Vercel manually allowlisting it first.
How it works
- The client hosts a JSON metadata document on its own domain and uses its HTTPS URL as the OAuth clientid
- This follows the MCP authorization spec, which now recommends CIMD over Dynamic Client Registration
Security & UX
- Since clients aren't reviewed by Vercel, the consent screen shows each one's name, logo, and metadata hostname (e.g. "Claude Code by claude.ai")
- CIMD clients get no verified badge — the hostname is what you're trusting on approval
- Users still log in and approve each connection; existing registered apps are unchanged
This resolves the top friction in MCP client-server interoperability: clients previously had to register with servers for a good experience.
More from coding & agent
- Act*ONOMY: a 120-category behavior taxonomy for annotating AI agent trajectories, at NeurIPS — DanielKhashabi · 2026-11-10
- opencode team runs everything in subagents to cut costs while keeping pricey model reviews — JensHonack · 2026-11-10
- Vork: an agent-native 3D engine with a ~2,500-token API renders 1M birds in 97s on one L4 GPU — ravisparikh · 2026-11-10
- Anthropic Staffs Up Claude Managed Agents to Run Thousands of Collaborating Agents Safely — threepointone · 2026-11-10
- Claude Code v2.1.322 adds Vertex fast mode across global, US and EU regions — claude-code-publisher[bot] · 2026-11-10
- Fable 5.2 hands-on: one-shots actually fun games, but one prompt cost $2,618 — arena · 2026-11-10