Vercel MCP Server 🚀

What is Vercel MCP Server?

A Model Context Protocol (MCP) server that provides full administrative control over Vercel deployments through Cursor’s Composer and Codeium’s Cascade. It enables seamless project management with comprehensive features for deployments, domains, environment variables, and more.

How to use Vercel MCP Server?

Clone the repository, install dependencies via npm install, build with npm run build, then configure your Vercel access token in the source files. Add the server to Cursor’s MCP settings using the absolute path to the built dist/index.js file along with your Node.js binary path. Once configured, describe your desired Vercel action (e.g., “List all my projects”) and the AI will execute the appropriate tool.

Key features of Vercel MCP Server

• Over a dozen tool categories covering team, project, deployment, and domain management
• Full DNS record creation, deletion, listing, and updating
• Environment variable, secret, and edge config CRUD operations
• Access group, authentication token, and firewall configuration tools
• Log drain, webhook, and web vitals monitoring capabilities
• Marketplace event, billing, and integration management

Use cases of Vercel MCP Server

• Create, list, or delete Vercel projects and deployments via natural language
• Add, update, or remove custom domains and DNS records for projects
• Manage environment variables, secrets, and edge configs across teams
• Set up access groups, firewall bypass rules, and authentication tokens
• Monitor deployments with log drains, webhooks, and web vitals analytics

FAQ from Vercel MCP Server

What runtime and accounts are required?

Node.js 16 or later, npm 8 or later, a Vercel account with a valid access token (and optionally a Team ID or Project ID), and either Cursor IDE or Codeium Cascade for paying users.

How do I debug or troubleshoot the server?

Add DEBUG=true before the command to see detailed logs. Common issues include incorrect Node.js path (use which node or where node), invalid or expired Vercel access token, or the MCP not detecting tools—refresh Cursor’s MCP settings or verify server is running without errors.

How is the Vercel access token handled?

The token must be placed in both src/config/constants.ts and src/index.ts. Keep it secure, never commit it to version control, and ensure it has the required permissions.

What transports and authentication does it use?

The server runs as a local MCP tool, started via a command line. Authentication is handled entirely by the Vercel access token passed in the configuration files; no additional transport layer is mentioned.

Are there any known limits or scalability constraints?

The README does not specify rate limits, concurrency caps, or dataset size restrictions. For production use, follow Vercel’s security best practices and use appropriate access controls.