Vercel
Deployment layer for managing Vercel projects, deployments, environment variables, and domains. Deploy, promote, rollback, and inspect from your agent context.
INSTALL THIS SERVER
{
"mcpServers": {
"vercel": {
"command": "npx",
"args": ["@vercel/mcp"],
"env": { "VERCEL_TOKEN": "your_token" }
}
}
}
16 TOOLS AVAILABLE
OUR ASSESSMENT
- First-party Vercel support with full API coverage
- Supports both stdio and streamable HTTP transport
- Deploy, promote, and rollback from agent context
- Environment variable management across preview and production
- Vercel-specific (covers Vercel deployments only)
- Some operations require team-level tokens
Vercel Access Tokens should be scoped to specific teams and projects. Use read-only tokens for monitoring workflows.
Agent-driven deployment management on the Vercel platform
TECHNICAL DETAILS
ADOPTION METRICS
// Reading thisFirst-party Vercel support drives organic star growth. The streamable HTTP transport option increased visibility.
// Reading thisDeployment automation is a high-frequency use case. Teams running CI/CD through agents install this early.
// Reading this#1 in Cloud. Globally #9 reflects the broad Vercel developer base.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 2 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
The same server, 2 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4editorial | 2,400 | 16.4K / wk | APR 22, 2026 |
| PulseMCP | 4.0 community | 860 | 8.2K / wk | APR 21, 2026 |
| Smithery | 4.1 installs | 860 | 9.4K installs | APR 20, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.