vercel

This MCP server provides a comprehensive interface to manage Vercel resources directly through Cursor's Composer. Once configured, you can issue natural language prompts describing the actions you want to perform on your Vercel projects, and the MCP server will route those requests to the appropriate Vercel API actions under the hood. Available capabilities include Team management (create, list, update, invite members), Project operations (list, create, delete, update, transfer), Deployment handling (create, cancel, list, get, manage deployment events and files), Domain and DNS management (add, remove, check, price, register, update DNS records, manage certificates), Environment and Edge Config (add/update env vars, manage edge configs and their items), Access control (auth tokens, firewall settings, and security configurations), Monitoring (webhooks, logs, analytics), and numerous integration points like marketplace and environment secrets. In practice, you can ask the MCP to list projects, deploy a new project, add a domain, or update environment variables, and it will call the corresponding MCP actions such as list_projects, create_deployment, add_domain, or add_env on your behalf. Examples you might try include asking to "list all my projects", "deploy a new production project with a staging URL", or "add an environment variable MY_API_KEY with value live-token to project X". The server acts as a centralized command broker that translates natural language requests into Vercel API calls via the defined MCP toolset. For Cursor's Composer users, configure the server in MCP settings with the appropriate command and path, then simply describe your desired outcome and let the AI orchestrate the steps.

Prerequisites:

• Node.js >= 16.x
• npm >= 8.x
• A Vercel account with an Access Token (and optional Team ID, Project ID)

Installation steps:

1. Clone the repository and install dependencies

   git clone https://github.com/Quegenx/vercel-mcp-server.git
   cd vercel-mcp-server
   npm install
   

2. Build the project (if applicable)

   npm run build
   

3. Obtain a Vercel access token:

   • Go to https://vercel.com/account/tokens and generate a token.
   • Keep it secure and do not commit to version control.

4. Configure MCP server in your environment:

   • Set the DEFAULT_ACCESS_TOKEN environment variable to your Vercel access token.
   • Ensure the server can be started with the Node.js entry point at dist/index.js.

5. Start the MCP server (example):

   node /path/to/vercel-mcp/dist/index.js
   

6. In Cursor MCP settings, add your server using the command format below (adjust path as needed):

   • Default Installation:

     /usr/local/bin/node /path/to/vercel-mcp/dist/index.js
     

   • macOS/Homebrew/NVM alternatives can point to the appropriate node executable, as shown in the README.

7. Verify:

   • Ensure the MCP server is reachable by your Cursor or Codeium integration and test a basic command like listing projects.

Prerequisites recap:

• Node.js 16+ and npm 8+ installed
• Valid Vercel access token
• Network access to Vercel APIs
• Cursor IDE or Codeium Cascade (for interacting via MCP)

Tips and common issues:

• Do not commit your Vercel access token. Use environment variables (DEFAULT_ACCESS_TOKEN) and secure storage.
• If the MCP server can't reach Vercel, verify network egress rules and token permissions.
• When configuring in Cursor, ensure you reference the correct dist/index.js path after building the project.
• The MCP supports a wide range of operations; if a requested action isn’t available, verify that the corresponding MCP tool (e.g., deployments, domains, env vars) is enabled and correctly wired in the server.
• Environment variables and secrets should be tested in a staging project before applying to production.