About vercel
An MCP server that manages Vercel deployments and exposes build and runtime application logs through the Vercel REST API. It suits developers and teams who want to inspect and debug deployments from an MCP client. Tool groups can restrict it to read-only access.
Key features
- 01Deployment list, inspect, create, cancel, delete, promote, rollback
- 02Build log retrieval for deployments
- 03Runtime log filtering by level, source, and time
- 04Readonly or readwrite tool groups via environment variable
- 05Team-scoped operations via team ID or slug
Use cases
- 01Check recent deployment states and find failed builds
- 02Read build output to diagnose deployment errors
- 03Promote a preview deployment to production or roll back
- 04Filter runtime logs for 500 errors or edge function issues
MCP support
This is an MCP server that exposes Vercel deployment and log operations as tools to MCP clients. Setting VERCEL_ENABLED_TOOLGROUPS=readonly disables all write operations.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y vercel-platform-mcp-serverVERCEL_TOKENSecretVercel API token for authentication.VERCEL_TEAM_IDTeam ID for team-scoped operations.VERCEL_TEAM_SLUGTeam URL slug for team-scoped operations.VERCEL_ENABLED_TOOLGROUPSComma-separated list of tool groups to enable (readonly, readwrite).Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
10Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| app | string | No | Filter by deployment name (the project name used in the URL). Example: "my-app" |
| limit | number | No | Maximum number of deployments to return (1-100). Default: 20. Use with pagination to page through results. |
| state | enum | No | Filter by deployment state. Options: "BUILDING", "ERROR", "INITIALIZING", "QUEUED", "READY", "CANCELED". Omit to return deployments in any state.BUILDING | ERROR | INITIALIZING | QUEUED | READY | CANCELED |
| until | number | No | Return deployments created before this timestamp (milliseconds since epoch). Used for pagination: pass the "next" value from a previous response. |
| target | enum | No | Filter by deployment target environment. Options: "production", "preview". Omit to return deployments for all targets.production | preview |
| projectId | string | No | Filter by project ID or name (e.g., "prj_abc123" or "my-app"). When set, only deployments for this project are returned. |
Details
From the project READMEVercel MCP Server
An MCP server for managing Vercel deployments and viewing application runtime logs through the Vercel REST API.
Highlights
- Deployment Management - List, inspect, create, cancel, delete, promote, and rollback deployments
- Build & Runtime Logs - View build logs (events) and runtime application logs for debugging
- Fine-grained Access Control - Enable readonly or readwrite tool groups via environment variables
- Team Support - Scope operations to a specific Vercel team
Capabilities
Tools
| Tool | Group | Description |
|---|---|---|
list_deployments | readonly | List deployments with filtering by project, target, and state |
get_deployment | readonly | Get detailed deployment information by ID or URL |
list_projects | readonly | List projects in the account/team |
get_deployment_events | readonly | Get build logs for a deployment |
get_runtime_logs | readonly | Get runtime application logs with filtering |
create_deployment | readwrite | Create a new deployment or redeploy |
cancel_deployment | readwrite | Cancel an in-progress deployment |
delete_deployment | readwrite | Delete a deployment permanently |
promote_deployment | readwrite | Promote a deployment to production |
rollback_deployment | readwrite | Rollback to a previous deployment |
Setup
Prerequisites
- A Vercel account with an API token (create one here)
- Node.js 18+
Configuration
| Variable | Required | Description |
|---|---|---|
VERCEL_TOKEN | Yes | Vercel API token |
VERCEL_TEAM_ID | No | Team ID for team-scoped operations |
VERCEL_TEAM_SLUG | No | Team URL slug (alternative to team ID) |
VERCEL_ENABLED_TOOLGROUPS | No | Comma-separated tool groups: readonly, readwrite (default: all) |
Manual Setup
# Clone the repository
git clone https://github.com/pulsemcp/mcp-servers.git
cd mcp-servers/experimental/vercel
# Install dependencies
npm install
# Build
npm run build
# Set environment variables
export VERCEL_TOKEN="your-token-here"
# Run
npm start
Usage Tips
- Use
list_projectsfirst to find project IDs needed bypromote_deployment,rollback_deployment, andget_runtime_logs - Runtime log retention varies by plan: Hobby=1h, Pro=1d, Enterprise=3d (up to 30d with Observability Plus)
- Use
get_runtime_logswithsince/untilto query historical logs,searchto find specific errors, andlevel/sourceto filter results - Set
VERCEL_ENABLED_TOOLGROUPS=readonlyto prevent any write operations - Use
list_deploymentswith thestatefilter to quickly find failed or in-progress deployments
Examples
Check deployment status
"What's the status of my latest deployments?"
Uses list_deployments to show recent deployments with their states.
Debug a failed build
"Show me the build logs for deployment dpl_abc123"
Uses get_deployment_events to display the build output and error messages.
Promote a preview to production
"Promote deployment dpl_abc123 to production for project prj_xyz789"
Uses promote_deployment to make a preview deployment serve production traffic.
View runtime errors
"Show me the runtime logs for my-app's latest deployment"
Uses list_projects to find the project ID, then get_runtime_logs to show recent application logs.
Search for specific errors in logs
"Find all 500 errors in the last 24 hours for my-app"
Uses get_runtime_logs with statusCode: 500 and since set to 24 hours ago to filter server errors.
Debug edge function issues
"Show me warning and error logs from edge functions for dpl_abc123"
Uses get_runtime_logs with source: "edge-function" and level: "error" to narrow down issues.
Development
# Install dependencies
npm install
# Build
npm run build
# Run functional tests
npm test
# Run integration tests
npm run test:integration
# Run manual tests (requires .env with VERCEL_TOKEN)
npm run test:manual
# Lint
npm run lint
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.