AgentsReady
Verified deep dive · Devtools

Vercel

Run the agent liveReport a change
4 minTime to key
NoNo-human path
1Human gates
9/10Onboarding score
Email verification

Fastest path to a key

  1. npm i -g vercel@latest
  2. Manual review
    `vercel signup` (new account) or `vercel login` (existing): OAuth 2.0 Device Flow; human approves in browser with Google / GitHub / Apple / ChatGPT / email
  3. Phone OTP
    if signup was by email: verify email (magic link/OTP)
  4. CLI session token is now usable for the CLI and `vercel api`; for a standalone bearer token: dashboard > Account Settings > Tokens > create scoped token (team scope + expiry)
  5. MCP: `npx -y add-mcp https://mcp.vercel.com -g` or `vercel mcp --clients "Claude Code"`, then OAuth consent in browser
  6. Working API key

Biggest gap

MCP OAuth is limited to Vercel-approved clients even though DCR exists, so custom agents and new clients are locked out. Claim Deployments needs the agent operator's own account

Worth copying

get-started.md: a playbook written for the agent to execute ('Perform actions yourself... Pause only for user authentication'), plus `vercel signup` so the agent can start account creation itself

Sources (10) · checked 2026-10-11
90Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context17/20
Interfaces32/32
Onboarding19/19
Trust2/9
llms.txt · root
MCP · https://mcp.vercel.com/mcp/sse
OpenAPI · https://vercel.com/openapi.json

Biggest gains

  1. +4 Agent manifests. Publish an MCP server card (/.well-known/mcp.json) or A2A agent card.
  2. +3 llms-full.txt exists. Publish /llms-full.txt with the whole docs corpus in one file.
  3. +3 Public status page. Link a status page so agents can tell outages from bugs.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • FAILllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • FAILAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 4 changes, up to +10 points

Each change is ready to paste, filled in for vercel.com, with a command to check it worked. Or hand the whole list to your coding agent.

A server card lets agents discover your MCP server from your domain alone.

Where: https://vercel.com/.well-known/mcp.json
{
  "name": "Vercel",
  "description": "<What an agent can do with Vercel, in one sentence>",
  "url": "https://mcp.vercel.com/mcp/sse",
  "transport": "streamable-http",
  "authentication": { "type": "oauth2", "resource_metadata": "https://mcp.vercel.com/.well-known/oauth-protected-resource" },
  "documentation": "https://docs.vercel.com",
  "tools": ["<tool_one>", "<tool_two>"]
}
Check it worked:curl -s https://vercel.com/.well-known/mcp.json

Add the badge to your README

AgentsReady badge for vercel.com
[![AgentsReady](https://agentsready.dev/badge/vercel.com)](https://agentsready.dev/c/vercel.com)