Claude Vercel connectorWhat Claude can do in your Vercel account.
The Claude Vercel connector exposes 7 tools on its directory sheet. 6 only read (docs, projects, deployments, teams), 0 write, and 1 is documented nowhere. Here is what Claude can check for you, what it cannot touch, and who controls the access.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for the people who ship the site
Instead of opening the Vercel dashboard, choosing a team, then a project, then a deployment, you ask Claude the question. It finds the team, reads the project and the deployment, and replies in the conversation. On the sheet, all of that is reading: nothing in this list changes your account.
Understand a broken preview. Someone sends a preview URL that shows an error. get_deployment reads that deployment's status from its hostname, and list_deployments puts it back in the project's history.
Map an inherited account. list_teams then list_projects tell you what exists, and get_project summarises one project's configuration in plain words.
Get a documented answer. search_vercel_documentation pulls the right page of Vercel's docs into the chat when you are unsure how something works.
What Claude will not do with this listing: deploy, cancel, roll back or edit a setting. The sheet exposes no such tool. Vercel's own reference describes many more tools than these seven, but the directory sheet is what this page follows. Nothing runs on its own either: no tool reacts when a build fails. For that kind of background alert, an automation tool is the right job; the Integrations hub covers that side.
The vocabulary in one minute
Five words you will see while plugging Vercel in.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work on it while it answers.
- Tool
- A named action a connector hands to Claude. Claude chooses on its own which ones to use; the directory sheet lists them.
- Authorization
- The service's own sign-in page, where you give Claude the access it will use. One grant per person, which you can take back.
- Approval
- The confirmation Claude waits for before completing an action that changes your account. It appears in the chat at that moment.
- MCP
- The shared standard behind connectors, which is what allows an assistant such as Claude to talk to an outside service.
Plug Vercel into Claude in three steps
- 01
Find Vercel in Claude
In Claude's settings, open Customize, then Connectors, and look for Vercel. On a Team or Enterprise workspace, an Owner or Primary Owner must enable the connector first, so that each member can then sign in on their own.
- 02
Start the connection
Click Connect on its row and sign in to Vercel in the window Vercel opens itself. If the link stops working one day, use Disconnect and connect it again.
- 03
Read the authorization screen
Go through the authorization screen before accepting. It is Vercel's screen, not Claude's, and it sets what the access covers. You can revoke that access later from your Vercel account as well.
The 7 tools, sorted by what they do
Vercel gives Claude 7 tools: 6 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups: what Claude reads, and what no official source describes. Names stay as Claude shows them, in English.
- 6 read
- 1 not documented
What Claude reads (6)
6 toolsSix tools that consult docs, teams, projects and deployments without changing them.
search_vercel_documentation
Searches Vercel's own documentation on a topic you name, custom domains for instance, and brings the relevant passages back into the chat so Claude can answer with Vercel's wording in mind.
list_projects
Lists the projects in your account or in a team you pick, with filters on the linked repository or on project settings.
get_project
Opens one project by its ID or name and returns its configuration, so Claude can tell you how it is set up before you touch anything.
list_deployments
Returns the deployments of your account, and can narrow them to a single project so the history stays readable.
get_deployment
Looks up one deployment by its ID or its hostname and reports its status and details.
list_teams
Shows the Vercel teams you belong to.
Undocumented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and a name is not a description.
get_deployment_events
The directory lists this name, and no official source describes it: Vercel's tool reference, read in September 2026, does not mention it at all. This page will not guess what it does.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. With this listing, none of the documented tools changes anything, so those requests should be rare.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time. They can also cap what a connector may do for the whole organization, for instance reading allowed, writing closed. That rule applies to everyone, and nobody lifts it from their own account. Vercel adds its own layer: your existing Vercel permissions still apply, and Claude only reaches the teams you granted at sign-in.
Which plans it is available on
None of the 819 sheets in the official directory shows availability per plan. The answer for a given connector is published nowhere, which is a real gap in the catalogue.
The general rule is public: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before members can sign in. Vercel's documentation says something narrower about adding it by hand; the limits section sets both side by side. The connector's sheet in the official directory is where the current state lives.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts by itself when a deployment fails or a domain changes.
The listing shows only reading, and that is an observed floor rather than a guarantee: an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic says on every sheet that it neither chooses a publisher's tools nor guarantees their behaviour. Vercel is documented only by its publisher here, with no Claude help article. For a connector that does write, compare with the Claude asana connector.
Which plans can use this connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner enables each one first.
- Vercel MCP documentation ↗September 2026The publisher states that custom connectors in Claude are available on Pro, Max, Team and Enterprise plans.
What this page followsNeither is stale, and they do not describe the same thing: Vercel's sentence is about adding the server by hand as a custom connector, Anthropic's rule covers directory connectors. It is the publisher speaking, not Anthropic, so check the directory sheet from your own account before relying on either.
Need help connecting Vercel to Claude?
A person reads every message.
