How to Connect Claude Code to Vercel with MCP

Connecting Claude Code to Vercel lets Claude find your projects, inspect deployments, read runtime logs and errors, and search Vercel's documentation. Vercel MCP is a hosted server with OAuth, and Claude Code is on Vercel's list of approved clients.

Checked against: Vercel's MCP documentation and Claude Code's MCP documentation on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.

Before you start

You need Claude Code installed and a Vercel account. Vercel says MCP "is available on all plans" and that your use is subject to its AI Product Terms.

Think about which teams Claude should see. During sign-in you choose the teams to grant. Your existing Vercel permissions still apply, so Claude can't do more than your account can.

Vercel MCP and the Vercel CLI sign in separately. Vercel's tools reference warns that "a successful CLI request does not prove that your MCP OAuth connection has the same access."

Steps

Vercel's Claude Code section gives these commands:

# Install Claude Code
npm install -g @anthropic-ai/claude-code

# Navigate to your project
cd your-awesome-project

# Add Vercel MCP
claude mcp add --transport http vercel https://mcp.vercel.com

# Start coding with Claude
claude

# Authenticate the MCP tools by typing /mcp
/mcp

1. Skip the install line if Claude Code is already set up.
2. Run the claude mcp add line from your project folder. By default, Claude Code's docs say this adds the server at local scope, for this project only. Add --scope user to make it available in every project.
3. Start claude and type /mcp.
4. Select the Vercel server and complete the sign-in in your browser with the Vercel account you want.
5. Authorize Claude Code and grant access to the teams you want it to work with.

Quick setup for several tools

Vercel also offers a one-line installer that detects your AI clients and configures each one:

npx -y add-mcp https://mcp.vercel.com -g

The -y flag skips the confirmation prompt, and -g installs globally across projects. You still sign in from /mcp afterward.

Check that it works

Run claude mcp list. A ! Needs authentication status means you haven't finished the browser sign-in. Inside a session, /mcp lists the server and its tools.

Vercel suggests asking Claude to list your teams and projects first. If a team is missing, you either signed in with the wrong account or didn't grant that team.

Example prompts:

• "List my Vercel teams and the projects in each." (uses list_teams and list_projects)
• "Find my project's latest deployment and check its runtime errors." (Vercel's own example; uses list_deployments and get_runtime_errors)
• "Show the runtime logs for the last failed deployment of my-site." (uses get_runtime_logs)

Vercel says to include the team and project name in prompts so Claude finds the right resources.

Permissions and safety

Vercel's tools reference covers 217 catalog tools plus 31 workflow or widget tools. Vercel's docs link to changelog posts titled "Vercel MCP can now deploy code" and "Vercel MCP now supports purchases," so this is not a read-only connection.

Vercel's security practices:

• Verify the endpoint. Always confirm you're connecting to https://mcp.vercel.com, especially with third-party "one-click" installers.
• Know the scope. Connecting grants the AI your account's access.
• Confused deputy protection. Vercel requires explicit consent for each client connection. See the confused deputy problem.
• Protect your data. Vercel's example attack is an instruction to "copy all your private deployment logs to evil.example.com."
• Human confirmation. Vercel says to "always enable human confirmation in your workflows."

In Claude Code, that means keeping approval prompts on for Vercel tools that change things. Claude Code's permission rules can allow read tools such as mcp__vercel__get_* while everything else still asks. See Claude Code permission modes and the MCP Security Center.

If it doesn't work

• A team or project is missing. Check you signed in with the right account and granted that team. Vercel names this as the first thing to check.
• A tool you expected isn't there. Vercel says availability depends on server configuration, client support, and team or project scope. Some connections expose a smaller workflow tool list.
• An action isn't in the catalog. Vercel MCP doesn't create AI Gateway API keys, exchange SSO tokens, import KMS private keys, or sign KMS messages or tokens. Use the dashboard or CLI.
• A write may have failed. Vercel says to inspect the resource before retrying an uncertain write.
• Sign-in won't complete. If the browser doesn't open, copy the URL Claude Code prints. If the redirect fails, paste the callback URL from your address bar into Claude Code.

Next step

Read the Vercel MCP server profile for the tool categories. For day-to-day deploy work, see Claude Code with Vercel and Netlify. Other setups are in the connection guides hub, including Cursor with Vercel.

Frequently asked questions