vercel mcp

The vercel mcp command helps you set up MCP clients (Claude Code, Claude.ai and Claude for desktop, Cursor, and VS Code with Copilot) to use Vercel MCP, Vercel's hosted Model Context Protocol endpoint at https://mcp.vercel.com. For Claude Code, Cursor, and VS Code with Copilot, the command configures the client directly. For Claude.ai and Claude for desktop, it prints manual setup instructions for adding a custom connector.

By default, clients are pointed at the shared endpoint. With --project, they're pointed at a project-specific URL (https://mcp.vercel.com/<org>/<project>) so the MCP session is scoped to the linked Vercel Project.

The command does not deploy any MCP server of your own. It only adjusts the client-side configuration on your machine.

vercel mcp [options]

By default, vercel mcp runs an interactive picker that lets you choose which MCP clients to set up. In non-interactive environments such as CI, you must pass --clients to skip the picker.

vercel mcp

vercel mcp --clients "Cursor,VS Code with Copilot"

vercel mcp --project

These are options that only apply to the vercel mcp command.

The --clients option accepts a comma-separated list of MCP clients to set up. In interactive mode, it skips the client picker. In non-interactive mode (for example, CI), --clients is required.

Supported values:

• Claude Code
• Claude.ai and Claude for desktop
• Cursor
• VS Code with Copilot

vercel mcp --clients "Cursor,VS Code with Copilot"

The --project option sets up project-specific MCP access for the currently linked project instead of global configuration.

vercel mcp --project

The following global options can be passed when using the vercel mcp command:

• --cwd
• --debug
• --global-config
• --help
• --local-config
• --no-color
• --non-interactive
• --scope
• --team
• --token
• --version

For more information on global options and their usage, refer to the options section.