$ claude mcp add --transport http vercel https://mcp.vercel.com copy
Vercel’s official remote MCP server, hosted by Vercel.
Why it matters
When a deployment fails, you open the Vercel dashboard and dig through build logs. Connect the Vercel MCP and you can read deployment state and logs to find the cause — and search the docs — from Claude Code.
What you can do
Representative tasks from Vercel’s official docs:
- Investigate failed builds — “Why did my latest production deployment fail?” (build logs)
- Debug runtime errors — “Show me the runtime error logs for my project from the last hour.”
- Search docs — “How do I configure custom domains in Vercel?”
- Inspect deployments — “Show me all deployments for my blog project.”
- Share protected deployments — “myapp.vercel.app is protected by auth. Create a shareable link for it.”
- Deploy — “Deploy this project to Vercel.”
Grounded in vercel.com/docs/agent-resources/vercel-mcp/tools.
Key features
- Documentation —
search_documentation - Projects and teams —
list_projects,get_project,list_teams - Deployments —
list_deployments,get_deployment,get_deployment_build_logs,get_runtime_logs - Domains —
check_domain_availability_and_price,buy_domain - Access and deploy —
get_access_to_vercel_url,deploy_to_vercel,use_vercel_cli
Setup
claude mcp add --transport http vercel https://mcp.vercel.com
After adding, run /mcp to complete the OAuth flow. To scope the session to one project, use a project URL of the form https://mcp.vercel.com/<team>/<project>.
Notes
- Remote-hosted — OAuth auth
- Public tools like documentation search work without auth; project and account tools require authentication
- Confused-deputy protection requires explicit user consent per client connection
- In Claude.ai and Claude Desktop, add it as a custom connector (Settings → Connectors)