Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Vercel to Claude Code

Let Claude trigger deploys and manage environment variables in Vercel. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Vercel to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Vercel, you add a Vercel MCP server: a small hosted service that exposes Vercel's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Vercel account. No API keys pasted into config files.

claude mcp add --transport http vercel https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Vercel once connected?

Full read-write Vercel access lets Claude trigger a deployment, promote a build to production, set or update environment variables, assign a domain, and manage project settings once you approve. The deploy and configuration work that used to mean switching to the dashboard happens where your project already lives.

  • Trigger a deployment or redeploy a project from the latest commit
  • Promote a preview deployment to production after you approve
  • Set, update, or remove environment variables for a project
  • Assign or update a custom domain on a project
  • Roll back to a previous production deployment
  • Update project settings such as build command or framework preset

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Vercel access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Vercel API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Vercel changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Vercel connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Vercel connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Vercel account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Vercel's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Vercel?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Vercel account it signs in with. Revoking access is one click in Vercel.

More on the Vercel connector

Vercel connector for claude.aiBitbucket + Claude CodeCircleCI + Claude CodeJenkins + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us