Reference MCP stdio server for observing Vercel projects and deployments.
Reference MCP stdio server for observing Vercel projects and deployments. Exposed over MCP by the vercel mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
list_projects — List projects visible to the configured account/team (search, limit)get_project — Fetch one project by ID or namelist_deployments — List recent deployments (filter by project, state, limit)get_deployment — Fetch one deployment by ID or URL, including current stateInstallation goes through your MCP client rather than a global install: point it at @addiplus/vercel-deployment-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: VERCEL_TOKEN, VERCEL_TEAM_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vercel's toolset — list_projects, get_project, list_deployments and 1 more — is a fair guide to whether it matches your workflow. It is maintained by addiplus; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Vercel's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_projects | List projects visible to the configured account/team (search, limit) |
| get_project | Fetch one project by ID or name |
| list_deployments | List recent deployments (filter by project, state, limit) |
| get_deployment | Fetch one deployment by ID or URL, including current state |
{
"mcpServers": {
"vercel-deployment": {
"command": "npx",
"args": ["-y", "@addiplus/vercel-deployment-mcp"],
"env": { "VERCEL_TOKEN": "…" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| VERCEL_TOKEN | Credential the server authenticates with. | Yes |
| VERCEL_TEAM_ID | Configuration value read at startup. | Optional |
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.