Vercel Deployment MCP
A community reference implementation of a stateless stdio MCP server designed to observe Vercel projects and deployments. It provides four read-only tools to list projects, fetch project details, list recent deployments, and fetch specific deployment states. The server handles configuration cleanly and behaves predictably on short-lived infrastructure, serving as a demonstration of deployment-focused MCP patterns rather than a replacement for Vercel's official offerings.
Package and access
Local package with source-attributed installation metadata. Koskamo does not execute packages during review.
What you can do with it
- List projects visible to the configured account or team
- Fetch details of a specific project by ID or name
- List recent deployments with filters for project, state, and limit
- Fetch a specific deployment by ID or URL to check its current state
Source and maintenance
- Maintenance checked
Packages and installation
Source-provided package data. Koskamo has not executed or live-probed this package.
@addiplus/vercel-deployment-mcp 0.2.0
{
"version": "0.2.0",
"transport": "stdio",
"identifier": "@addiplus/vercel-deployment-mcp",
"registryType": "npm",
"registryBaseUrl": "https://registry.npmjs.org",
"environmentVariables": [
{
"name": "VERCEL_TOKEN",
"isRequired": true,
"description": "Vercel API access token used to read project and deployment information. Create one at https://vercel.com/account/tokens."
},
{
"name": "VERCEL_TEAM_ID",
"description": "Optional Vercel team (scope) identifier. Set this when the token belongs to a team so requests target the correct team scope."
}
]
}Tools
Reported by the attributed source; not independently observed by Koskamo.
Connect from your client
Each snippet configures the same source-provided package; replace placeholders before use.
Cursor
{
"mcpServers": {
"vercel-deployment-mcp": {
"command": "npx",
"args": [
"-y",
"@addiplus/vercel-deployment-mcp@0.2.0"
],
"env": {
"VERCEL_TOKEN": "<YOUR_VERCEL_TOKEN>",
"VERCEL_TEAM_ID": "<YOUR_VERCEL_TEAM_ID>"
}
}
}
}Cline
{
"mcpServers": {
"vercel-deployment-mcp": {
"command": "npx",
"args": [
"-y",
"@addiplus/vercel-deployment-mcp@0.2.0"
],
"env": {
"VERCEL_TOKEN": "<YOUR_VERCEL_TOKEN>",
"VERCEL_TEAM_ID": "<YOUR_VERCEL_TEAM_ID>"
}
}
}
}VS Code
{
"servers": {
"vercel-deployment-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@addiplus/vercel-deployment-mcp@0.2.0"
],
"env": {
"VERCEL_TOKEN": "<YOUR_VERCEL_TOKEN>",
"VERCEL_TEAM_ID": "<YOUR_VERCEL_TEAM_ID>"
}
}
}
}Claude Desktop
{
"mcpServers": {
"vercel-deployment-mcp": {
"command": "npx",
"args": [
"-y",
"@addiplus/vercel-deployment-mcp@0.2.0"
],
"env": {
"VERCEL_TOKEN": "<YOUR_VERCEL_TOKEN>",
"VERCEL_TEAM_ID": "<YOUR_VERCEL_TEAM_ID>"
}
}
}
}Let your agent find its tools
Find servers like Vercel Deployment MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.