Deployments, logs and projects from Vercel's official hosted server — ship and debug without the dashboard.
Vercel's official MCP server at mcp.vercel.com gives assistants a hosted, OAuth-authenticated line into your Vercel account: projects, deployments, build and runtime logs, plus documentation search — the operational surface of shipping on Vercel, minus the dashboard tabs.
The deploy-debug loop is the core value. "Why did the last production deployment fail?" walks the assistant into the actual build logs, where the real error (the type mismatch, the missing env var, the ESM/CJS incident) lives — read, interpreted and, if your coding assistant has repo access, often fixed in the same conversation. That loop — deploy fails, assistant reads logs, assistant patches code, redeploy — is one of the tightest agentic workflows currently available anywhere.
Beyond firefighting, it answers the fleet-management questions that accumulate around an account: which projects exist, what domains point where, which deployments are on which branches, what changed between Friday's working deploy and Monday's broken one. Docs search grounds platform questions in current Vercel documentation, which matters for a platform iterating as quickly as this one.
Being an official hosted server, setup is one URL plus an OAuth approval, and access rides your Vercel login with its existing team scoping. Client support is broad (Claude, Cursor, VS Code, Devin and friends). If your deploys land on Vercel, this plus a repo-connected coding assistant is the shortest path from "build failed" to "fixed and shipped" that exists right now.
list_teams first when you belong to several, or a personal-account default will hand back a confusingly empty project list.next.config.js, commits, and watches the redeploy go green.Build logs read and interpreted the moment a deployment goes red.
Projects, domains and deployment states across an account, answered directly.
With repo access alongside: fail → read logs → patch → redeploy, in one thread.
| Tool | What it does |
|---|---|
| list_projects / get_project | Enumerate and inspect projects |
| list_deployments / get_deployment | Deployment history and status |
| get_deployment_build_logs | Read build logs — the deploy-failure goldmine |
| get_runtime_logs | Runtime/function logs for live debugging |
| search_documentation | Search current Vercel docs |
| list_teams | Team context for scoped operations |
claude mcp add --transport http vercel https://mcp.vercel.comOAuth approval in the browser; access follows your Vercel account and teams.
A Vercel account; OAuth handles the rest. No local install for HTTP-capable clients.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.