Installation

Choose your preferred installation method and IDE below.

Get Your Vercel API Token

Before configuring any IDE, you need a Vercel API token:

Go to Vercel Account Settings > Tokens
Click Create Token, give it a name, and select the appropriate scope
Copy the token value

Optional — Team ID:

To scope all queries to a specific Vercel team, set VERCEL_TEAM_ID. Find it in your team's General Settings URL (https://vercel.com/teams/<team-slug>/settings — the Team ID is shown on that page).

caution

Never commit your Vercel token to version control. Always use environment variables or IDE-specific secret management.

Option A: Via npx (Recommended)

No installation needed. Your IDE will run the server on demand:

npx -y @vineethnkrishnan/vercel-mcp

This is the simplest method — just reference it in your IDE config below.

Option B: Global Install

npm install -g @vineethnkrishnan/vercel-mcp

Then use vercel-mcp as the command in your IDE config (instead of npx).

Option C: From Source

git clone https://github.com/vineethkrishnan/mcp-pool.git
cd mcp-pool
npm install
npm run build

Then use node /absolute/path/to/mcp-pool/packages/vercel/build/index.js as the command.

IDE Configuration

Claude Desktop

Config file location:

OS	Path
macOS	`~/Library/Application Support/Claude/claude_desktop_config.json`
Windows	`%APPDATA%\Claude\claude_desktop_config.json`
Linux	`~/.config/Claude/claude_desktop_config.json`

Quick access: Settings > Developer > Edit Config

Using npx:

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token",
        "VERCEL_TEAM_ID": "team_optional"
      }
    }
  }
}

Using global install:

{
  "mcpServers": {
    "vercel": {
      "command": "vercel-mcp",
      "env": {
        "VERCEL_TOKEN": "your-vercel-token"
      }
    }
  }
}

From source:

{
  "mcpServers": {
    "vercel": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-pool/packages/vercel/build/index.js"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token"
      }
    }
  }
}

tip

Restart Claude Desktop completely after editing the config. Changes are not picked up automatically.

VS Code (GitHub Copilot)

Config file location:

Scope	Path
Workspace	`.vscode/mcp.json` (in your project root)
User (macOS)	`~/Library/Application Support/Code/User/mcp.json`
User (Windows)	`%APPDATA%\Code\User\mcp.json`
User (Linux)	`~/.config/Code/User/mcp.json`

Quick access: Command Palette (Cmd+Shift+P) > MCP: Open User Configuration

warning

VS Code uses "servers" as the root key, not "mcpServers".

Workspace config (.vscode/mcp.json):

{
  "servers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "${input:vercel-token}",
        "VERCEL_TEAM_ID": "${input:vercel-team-id}"
      }
    }
  },
  "inputs": [
    {
      "id": "vercel-token",
      "description": "Vercel API Token",
      "type": "password"
    },
    {
      "id": "vercel-team-id",
      "description": "Vercel Team ID (optional, press Enter to skip)",
      "type": "promptString"
    }
  ]
}

The inputs feature prompts you for the token securely — it never gets stored in the file.

User config (without inputs):

{
  "servers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token"
      }
    }
  }
}

Cursor

Config file location:

Scope	Path
Global	`~/.cursor/mcp.json`
Project	`.cursor/mcp.json` (in your project root)

Quick access: Settings > Cursor Settings > MCP

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token",
        "VERCEL_TEAM_ID": "team_optional"
      }
    }
  }
}

Project-level config (.cursor/mcp.json) takes precedence over global config.

Windsurf (Codeium)

Config file location:

OS	Path
macOS / Linux	`~/.codeium/windsurf/mcp_config.json`
Windows	`%USERPROFILE%\.codeium\windsurf\mcp_config.json`

Quick access: Settings > Advanced Settings > Cascade section

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token",
        "VERCEL_TEAM_ID": "team_optional"
      }
    }
  }
}

tip

Make sure MCP is enabled in Windsurf: Settings > Advanced > Cascade > Enable MCP.

JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)

JetBrains IDEs (2025.2+) support MCP servers through the settings UI.

Setup:

Open Settings/Preferences > Tools > AI Assistant > MCP Servers
Click + Add to add a new server
Configure:
- Name: vercel
- Command: npx
- Arguments: -y @vineethnkrishnan/vercel-mcp
- Environment Variables: VERCEL_TOKEN=your-vercel-token;VERCEL_TEAM_ID=team_optional
Click OK and restart the AI Assistant

Alternative — manual config file:

Create or edit ~/.config/JetBrains/mcp.json:

{
  "mcpServers": {
    "vercel": {
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token",
        "VERCEL_TEAM_ID": "team_optional"
      }
    }
  }
}

Claude Code (CLI)

Option 1 — CLI command (recommended):

claude mcp add vercel \
  --scope user \
  -e VERCEL_TOKEN=your-vercel-token \
  -e VERCEL_TEAM_ID=team_optional \
  -- npx -y @vineethnkrishnan/vercel-mcp

Scope options:

--scope user — available in all your projects
--scope local — current project only (default)
--scope project — shared with team via .mcp.json

Option 2 — manual config:

Edit ~/.claude.json (user scope) or .mcp.json (project scope):

{
  "mcpServers": {
    "vercel": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@vineethnkrishnan/vercel-mcp"],
      "env": {
        "VERCEL_TOKEN": "your-vercel-token",
        "VERCEL_TEAM_ID": "team_optional"
      }
    }
  }
}

Verify it's working:

claude mcp list

Environment Variables

Variable	Required	Description
`VERCEL_TOKEN`	Yes	Vercel API token from Account Settings > Tokens
`VERCEL_TEAM_ID`	No	Vercel Team ID. When set, all API calls are scoped to that team.

Verify Installation

After configuring your IDE, test the connection by asking your AI assistant:

"List my Vercel projects."

If the server is working, you'll get a response with your projects. If not, check:

Token is valid — test with curl -H "Authorization: Bearer your-token" https://api.vercel.com/v9/projects
Node.js >= 20 — run node --version
Config file syntax — validate your JSON (no trailing commas)
Restart your IDE — most IDEs require a full restart after config changes

Get Your Vercel API Token​

Option A: Via npx (Recommended)​

Option B: Global Install​

Option C: From Source​

IDE Configuration​

Claude Desktop​

VS Code (GitHub Copilot)​

Cursor​

Windsurf (Codeium)​

JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)​

Claude Code (CLI)​

Environment Variables​

Verify Installation​

Get Your Vercel API Token

Option A: Via npx (Recommended)

Option B: Global Install

Option C: From Source

IDE Configuration

Claude Desktop

VS Code (GitHub Copilot)

Cursor

Windsurf (Codeium)

JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)

Claude Code (CLI)

Environment Variables

Verify Installation