# Vercel MCP

> Manage Vercel deployments, domains, and environment variables through conversation. This MCP lets your AI client take full control of complex deployment pipelines. You can list all projects across teams, inspect build logs for errors, track domain SSL status, and even cancel running builds—all without navigating the Vercel dashboard. It puts enterprise-grade DevOps operations right into your natural workflow.

## Overview
- **Category:** loved-by-devs
- **Price:** Free
- **Tags:** deployment, frontend-cloud, serverless, git-integration, environment-variables, edge-network

## Description

Connecting this MCP gives your AI agent full visibility into your entire deployment stack. Instead of logging into multiple dashboards to check build statuses or hunt for credentials, you simply ask your client to do it. You can list all projects with their framework and latest status. Need to debug a failing release? Your agent fetches the runtime logs instantly. Want to update a secret key? It handles creating or deleting environment variables scoped exactly to production or preview environments. Furthermore, you'll get an accurate inventory of custom domains, checking SSL health and DNS records on demand. This integration turns your AI client into a dedicated deployment engineer that knows where everything lives, making it part of the Vinkius catalog of essential dev tools.

## Tools

### cancel_deployment
Cancels a running Vercel deployment by providing its unique ID.

### create_env_var
Adds a new environment variable to a specific project, allowing you to scope it to multiple target environments.

### delete_env_var
Permanently removes an existing environment variable from a Vercel project.

### get_deployment
Retrieves specific details for a single, identified Vercel deployment.

### get_domain
Fetches the configuration and status details for a specified custom domain name.

### get_logs
Retrieves runtime logs, useful for debugging issues by filtering by time or project ID.

### list_env_vars
Returns a list of all environment variables available in a project, showing keys but hiding values.

### list_projects
Provides an overview of all Vercel projects, listing their framework, git repository, and latest deployment status.

### list_teams
Lists every team within your account, providing the necessary IDs for use in other tools.

### get_user
Verifies your token connection by retrieving the authenticated Vercel user's basic profile information.

### get_project
Gets detailed information for a specific project, using either its ID or name.

### list_aliases
Lists all active deployment aliases (URLs) mapped to specific deployments within Vercel.

### list_deployments
Generates a list of all recent projects, showing their status, URL, and git commit information.

### list_domains
Lists every domain configured for the team, including its verification status and DNS records.

## Prompt Examples

**Prompt:** 
```
Show me the latest deployments for my portfolio project.
```

**Response:** 
```
I found 5 recent deployments for your portfolio project: the latest one (READY, deployed 2h ago from main branch), followed by a BUILDING deployment from 30m ago (PR #42), and an ERROR deployment from 3h ago that failed due to a build timeout.
```

**Prompt:** 
```
Add the STRIPE_SECRET_KEY env var to my production environment.
```

**Response:** 
```
Done! I've created the `STRIPE_SECRET_KEY` environment variable scoped to the production environment for your project. The value has been securely stored and will be available on the next deployment.
```

**Prompt:** 
```
Check if my custom domain example.com is properly configured.
```

**Response:** 
```
The domain example.com is VERIFIED with valid A records pointing to Vercel's IPs (76.76.21.21). SSL certificate is active and issued by Let's Encrypt. The apex domain and www subdomain are both configured correctly. No DNS misconfigurations detected.
```

## Capabilities

### Audit Deployment Status
List all projects and track their latest deployment status, including git commit information.

### Manage Environment Secrets
Create or delete environment variables across specific target environments like production or development.

### Inspect Build History
Retrieve detailed deployment history, including status changes, URLs, and commit data for every build.

### Monitor Domain Health
List all custom domains, checking their SSL certificate status and DNS verification records.

### Debug Build Failures
Fetch detailed runtime logs for any deployment to pinpoint exactly where a build or application failed.

## Use Cases

### Investigating a Failed Build
A developer notices an error on staging but doesn't know why. They ask their agent to get_logs for the failed deployment ID, immediately pinpointing a missing dependency in the build logs and fixing it.

### Pre-Launch Domain Audit
A team lead needs to confirm if two new custom domains are ready. They ask the agent to list_domains, verifying both SSL certificates are active and pointing to the correct IPs before marketing goes live.

### Secret Key Rotation
The security team mandates a key change. A DevOps engineer uses create_env_var to update the API key in production and list_env_vars to confirm the variable exists for all target environments, completing the rotation safely.

### Project Inventory Check
A new hire needs a full picture of the application stack. They use list_projects to get an immediate inventory, seeing every deployed app, its framework, and who owns it.

## Benefits

- Stop clicking through tabs. Instead of checking the Vercel dashboard for build status, simply ask your agent to list deployments or get project details.
- Manage credentials securely. You can use create_env_var or delete_env_var to update sensitive variables across production and development environments without manual UI work.
- Pinpoint errors instantly. If a deployment fails, running the get_logs tool fetches the necessary runtime logs immediately for debugging.
- Verify infrastructure health. Use list_domains and get_domain to audit custom domains, confirming SSL status and DNS records are correct before launch.
- Maintain visibility across teams. The MCP lets you list all projects or list_teams to understand who owns what, simplifying large-scale operations.

## How It Works

The bottom line is that your AI agent manages the complex Vercel API calls so you can focus on writing code.

1. Subscribe to this MCP and provide your Vercel Access Token.
2. Connect the MCP to your preferred AI client (like Cursor or Claude).
3. Tell your agent what you need—for example, 'List all projects in the marketing team' or 'Check the logs for deployment X'.

## Frequently Asked Questions

**How do I check my custom domains with Vercel MCP?**
You use list_domains to get a full inventory of all configured domains. This tool shows the verification status, DNS records, and SSL certificate health for every domain associated with your team.

**Can I update environment variables using Vercel MCP?**
Yes, you can manage secrets directly through the agent. Use create_env_var to set a new key-value pair or delete_env_var if a variable is outdated.

**What tool do I use for debugging deployment issues?**
Use get_logs. This function lets you retrieve runtime logs, and you can narrow down the search by project ID or specific time stamps to find the exact line of code causing the failure.

**How do I see all my available Vercel projects?**
You simply run list_projects. This gives you a comprehensive list showing every single deployed application, its framework, and when it was last updated.

**Does Vercel MCP help me cancel builds?**
Yes, if a build is running but needs to be stopped, use cancel_deployment. You just need the specific deployment ID for this action.

**How do I create a Vercel Access Token?**
Log in to the [**Vercel Dashboard**](https://vercel.com/account/tokens), go to **Settings > Access Tokens**, click **Create Token**, give it a name, select your team (optional) and scope. Copy the token immediately — it won't be shown again.

**Can I manage environment variables via the agent?**
Yes! Use `list_env_vars` to see all variable keys (values are hidden for security), `create_env_var` to add new ones with key, value and target environments (production, preview, development), and `delete_env_var` to remove them.

**Can I cancel a running deployment?**
Yes! Use `cancel_deployment` with the deployment ID to stop a build that is currently in progress. The deployment status will change to CANCELED. You can find the deployment ID from `list_deployments`.

**How do I check my deployment history?**
Use `list_deployments` optionally filtered by teamId and projectId to see recent deployments. Each entry shows the deployment URL, status (READY, BUILDING, ERROR), framework, git commit and creation date. Use `get_deployment` with a specific deployment ID for full details including build logs.