vercel-deployment-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERCEL_TOKEN | Yes | Vercel access token (create in account settings) | |
| VERCEL_TEAM_ID | No | Scope requests to a team | |
| VERCEL_MCP_MAX_CONCURRENT | No | Maximum number of Vercel API requests in flight at once (default `4`) | |
| VERCEL_MCP_MIN_INTERVAL_MS | No | Minimum milliseconds between the start of one Vercel API request and the next (default `250`) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List projects visible to the configured account or team. Optional text search and result limit. |
| get_projectA | Fetch one project by ID or name. |
| list_deploymentsA | List recent deployments, optionally filtered by project ID and state (e.g. BUILDING, ERROR, READY). |
| get_deploymentA | Fetch one deployment by ID or URL, including its current state. |
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 4 tools
Each tool is clearly distinct: list vs get for projects and deployments. There is no overlap between listing and fetching individual resources, making selection unambiguous.
All tool names follow a consistent verb_noun pattern with 'get' for single items and 'list' for collections, and nouns are appropriately singular or plural. The naming is predictable and uniform.
With 4 tools, the set is well-scoped for a read-only deployment monitoring server. It covers both projects and deployments with list and get operations, and each tool earns its place without unnecessary bloat.
For the apparent purpose of retrieving project and deployment information, the tool surface is complete. It provides list and get for both resources, with filtering options on deployments, leaving no obvious dead ends.