Vercel MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERCEL_API_KEY | Yes | Your Vercel API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getDeploymentEventsC | Gets deployment events by deployment ID and build ID |
| getDeploymentC | Gets a deployment by ID or URL |
| cancelDeploymentC | Cancels a deployment |
| listDeploymentFilesC | Lists deployment files |
| getDeploymentFileContentsD | Gets deployment file contents |
| getDeploymentsC | Lists deployments |
| deleteDeploymentC | Deletes a deployment |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose targeting different aspects of deployments. The actions (cancel, delete, get, list) are well-differentiated and operate on specific resources like deployments, events, files, or file contents with no overlap in functionality.
The naming follows a consistent verbNoun pattern with camelCase throughout, such as 'getDeployment' and 'listDeploymentFiles'. The only minor deviation is 'getDeploymentEvents' which uses plural 'Events' while others use singular or plural appropriately, but overall the pattern is highly predictable and readable.
With 7 tools, the count is well-scoped for managing deployments in a Vercel context. Each tool earns its place by covering essential operations like listing, retrieving, canceling, deleting, and accessing deployment details and files, without being excessive or insufficient for the domain.
The toolset provides strong coverage for deployment lifecycle management, including create (implied by deployment actions), read (get/list), update (cancel as a state change), and delete operations. A minor gap is the lack of explicit tools for creating or updating deployments, but core workflows are well-supported with no dead ends.