- Home
- MCP servers
- Vercel
Vercel
- typescript
60
GitHub Stars
typescript
Language
4 months ago
First Indexed
3 weeks ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"quegenx-vercel-mcp-server": {
"command": "node",
"args": [
"/path/to/vercel-mcp/dist/index.js"
]
}
}
}You run a MCP server that gives you central, programmable control over your Vercel deployments. This server exposes a comprehensive set of management actions for deployments, domains, environment variables, teams, projects, and more, all accessible through an MCP client. It lets you automate and orchestrate your Vercel workflows from familiar MCP interfaces.
How to use
Use your MCP client to describe the actions you want to perform on your Vercel projects. You can list projects, create new deployments, manage domains, set environment variables, and perform many other admin tasks through the available MCP endpoints. The server handles authentication, communicates with Vercel, and returns results you can use in your automation flows. You will typically start the MCP client, select the Vercel MCP server, and issue high-level intents like creating a deployment, adding a domain, or updating environment variables.
How to install
Prerequisites: ensure Node.js is installed (version 16 or newer) and npm is available (version 8 or newer). You also need a Vercel account with an access token; optional team and project identifiers may be needed for certain actions. Cursor IDE or Codeium’s Cascade is supported for paid users.
Step 1: Install dependencies and build the project.
# Install dependencies
npm install
# Build the project
npm run build
Step 2: Configure your Vercel access token in the codebase where the server reads it.
export const DEFAULT_ACCESS_TOKEN = "YOUR_ACCESS_TOKEN"; // in src/config/constants.ts
export const DEFAULT_ACCESS_TOKEN = "YOUR_ACCESS_TOKEN"; // in src/index.ts
Step 3: Run the MCP server as a local process via your MCP client configuration. The server is intended to be started with a Node runtime, typically using the dist/index.js entry.
# macOS/Linux (example paths; adjust to your installation)
/usr/local/bin/node /path/to/vercel-mcp/dist/index.js
# macOS with Homebrew
/opt/homebrew/bin/node /path/to/vercel-mcp/dist/index.js
# NVM installation
~/.nvm/versions/node/v18.x.x/bin/node /path/to/vercel-mcp/dist/index.js
Additional sections
Configuration, security, and troubleshooting information are provided to help you run the MCP server smoothly. Below are important notes and guidance pulled from the setup and usage details.
Security Notes
Keep your Vercel access token secure and do not commit it to version control. Use appropriate access controls and follow Vercel’s security best practices when managing tokens and permissions.
Troubleshooting
Common issues include path resolution for Node.js, valid Vercel tokens, and ensuring the MCP server is running without errors. If you encounter problems, verify the Node.js path with which node (macOS/Linux) or where node (Windows), check token validity and permissions, and ensure the server process is active. For deeper investigation, enable debug logs by prefixing commands with DEBUG=true.
# macOS/Linux
DEBUG=true /usr/local/bin/node /path/to/vercel-mcp/dist/index.js
# Windows
set DEBUG=true && "C:\Program Files\nodejs\node.exe" "C:\path\to\vercel-mcp\dist\index.js"
Available tools
list_teams
List teams in your MCP setup and access team-level management features.
create_team
Create a new team under your MCP management and assign members.
delete_team
Remove a team and revoke its access.
list_projects
Retrieve all projects available in your Vercel workspace.
create_project
Create a new Vercel project and configure initial settings.
delete_project
Delete a project from your Vercel workspace.
update_project
Update project metadata and settings.
pause_project
Pause deployment activity for a project.
add_env
Add environment variables to a project.
update_env
Update existing environment variables for a project.
delete_env
Remove environment variables from a project.
get_env
Retrieve environment variables for a project.
list_env
List all environment variables for a project.
add_domain
Attach a domain to a project.
remove_domain
Detach a domain from a project.
get_domain
Fetch details about a domain bound to a project.
list_domains
List all domains associated with a project.
create_deployment
Create a new deployment for a project.
cancel_deployment
Cancel an ongoing deployment.
get_deployment
Get details about a specific deployment.
delete_deployment
Delete a deployment from history.
list_deployment
List deployments for a project.
promote_deployment
Promote a deployment to a live environment.
get_promotion_aliases
Fetch available promotion aliases for deployments.