vercel

This MCP server provides a unified interface to manage Vercel projects, deployments, environment variables and domains via the Model Context Protocol. It exposes a set of MCP tools such as vercel_list_projects, vercel_get_project, vercel_list_deployments, vercel_get_deployment, vercel_list_env_vars, vercel_create_env_var, vercel_update_env_var, vercel_delete_env_var, vercel_list_domains, vercel_add_domain, vercel_delete_domain, and higher-priority tools for runtime and build logs, webhooks, teams, and analytics. To use it, configure your MCP client (e.g., Trae) to point at the vercel MCP server entry, supplying your Vercel API token and an optional Vercel team ID. The server authenticates requests via the Vercel API token and returns standardized MCP responses for all supported operations.

Prerequisites:

• Node.js and npm installed
• A Vercel API Token with appropriate permissions
• Optional: a path for your local vercel-mcp-server project if you choose the node-based invocation

Install and setup:

1. Clone the repository and install dependencies

git clone <repository-url>
cd vercel-mcp-server
npm install

2. Build the project (required before running via node)

npm run build

3. Obtain a Vercel API Token as described in the README and set it in your environment when running the MCP server configuration (see mcp_config below).

4. Run or configure the MCP server in Trae or your MCP client using the provided configuration example (see JSON in mcp_config).

Tips and considerations:

• Ensure you have run npm run build before attempting to start the server via the node entry point or the npx invocation.
• Set VERCEL_TOKEN securely and avoid committing it in configuration files.
• The repository includes guidance for both npx-based startup (recommended) and a direct node command as a fallback.
• If paths or tokens are incorrect, you may encounter API authentication errors or ENOENT issues; verify dist/index.js exists after build and that the provided absolute path is correct in your environment.
• LOG_LEVEL can be adjusted (e.g., debug) for troubleshooting during development.
• The MCP server uses standard MCP response formats; integrate with Trae or another MCP client that supports stdio-based MCP connections.