Skip to content

CI

Vercel MCP connector

The Vercel connector brings your Vercel teams, projects, members and environment variables into Claude, ChatGPT, Cursor and any MCP client, so each person can ask about and manage them inside their own Vercel access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Vercel to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Vercel once

  1. Open Connections, choose Add connection, and pick Vercel.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Vercel API key. One person generates a token in Vercel and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

vercel
Vercel
1Password
360learning
7shifts
Acquire
Ada
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Vercel to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Vercel to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Vercel to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Vercel to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Vercel through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Set up a new project with its variables

    Create a Vercel project for a new site or service and add the environment variables it needs in one conversation, instead of clicking through the settings pages one field at a time.

  • Platform

    Pause a project that should not be live

    Pause a Vercel project that is no longer needed, is running up usage, or is misbehaving, then confirm which projects on the team are still active.

  • IT

    Get a new hire onto the right projects

    Add a new teammate as a Vercel member and put them on the projects they will work on, using the role you name, without opening each project separately.

  • Security

    Review who can reach which project

    List every Vercel member and every project member across your teams to spot people with more access than their job needs, and remove access that should not be there.

  • Marketing

    Check the setup behind the company website

    Ask which Vercel project runs the marketing site, who is on it, and which environment variables are configured, without waiting for an engineer to look it up.

  • Operations

    Remove a leaver from every project

    When someone leaves, take them off each Vercel project they belonged to and remove them from the team, then confirm nothing was missed.

Try asking

  • “List Vercel projects created this week and their owners.”
  • “Which Vercel team members have access to the checkout project?”
  • “Summarize deployment activity across all Vercel projects this month.”

See all 84 Vercel tools below

AI tools

Vercel tools for your AI agents

84 tools are ready to call through Elaichi's MCP endpoint the moment you connect Vercel, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Vercel gets you

6 screens from the product, each doing one job for your Vercel account.

The agent

Ask about Vercel projects in plain language.

Starter prompts return answers from live Vercel projects, deployments and team members.

  • projects
  • deployments
  • teams
  • members

Ask Elaichi to work across your apps.

List Vercel projects created this week and their owners.

Which Vercel team members have access to the checkout project?

Summarize deployment activity across all Vercel projects this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Vercel here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

84 Vercel tools are ready to call.

Teams, members, projects and deployments are covered with no custom code written.

  • List all Vercel teams
  • Get single Vercel team by ID
  • Create a Vercel team
  • Update a Vercel team by ID
ElaichiTools
Tool Action Description
List all Vercel teams List List Vercel teams. Returns team records including id, slug, name, description, avatar, and emailDomain. Optionally filter by slug, search text, role, or timestamp range.
Get single Vercel team by ID Get Get a Vercel team by id. Returns the team record including id, slug, name, description, avatar, and emailDomain. Required: id.
Create a Vercel team Create Create a new Vercel team. Returns the id and slug of the newly created team. Required: slug.
Update a Vercel team by ID Update Update a Vercel team's settings by id. Returns the updated team record including id, slug, name, description, avatar, and emailDomain. Required: id.
Delete a Vercel team by ID Delete Delete a Vercel team by id. Returns an empty 204 response on success. Required: id.

Toolboxes

Every team gets its own Vercel toolbox.

Curate one toolbox per team so each sees only relevant Vercel tools.

  • Frontend
  • Platform
  • Release
  • QA
ElaichiToolboxes
Name Source template Tools Created

Frontend toolbox

Vercel · projects and deployments

Vercel starter 18 Mar 4, 2026

Platform toolbox

Vercel · teams and access

9 Mar 2, 2026

Release toolbox

Vercel · production deployments

24 Feb 27, 2026

QA toolbox

Vercel · preview deployments

Vercel starter 6 Feb 19, 2026

Security toolbox

Vercel · members and permissions

31 Jan 30, 2026

Docs toolbox

Vercel · documentation projects

12 Jan 22, 2026

Shared connections

Teammates use Vercel without holding the token.

Each connection shows who connected it and which teams and members share it.

  • Web platform
  • Marketing site
  • Internal tools
  • Release engineering
ElaichiConnections
Connection Scope Status Access
VE

Vercel (Web platform)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
VE

Vercel (Marketing site)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
VE

Vercel (Internal tools)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
VE

Vercel (Release engineering)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
VE

Vercel (Docs site)

Connected by Clara Nowak

Personal • Active Not shared
VE

Vercel (Prototypes)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Vercel call is on the record.

When, who, what happened, type and resource, appended for each project and deployment.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Vercel Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Vercel Projects Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Vercel Projects List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule ships a Vercel deployment digest.

Six steps fetch deployments, group them, draft a digest, await approval, then post back.

Vercel digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch projects

    Vercel

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Vercel

    Queued

Collections and dashboards

Vercel deployment health, computed on a schedule.

Four metrics, a 14 day chart of deployments created, and a breakdown by team.

Vercel health

Refreshed 4 minutes ago · every 15 minutes · from the projects collection

Live

Projects

1,284 ↓ 12%

Deployments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Projects created

Last 14 days

By team

Share of activity

Web platform 34%

Marketing site 27%

Internal tools 21%

Release engineering 18%

FAQ

Frequently asked questions

How do I connect Vercel to Claude?

Connecting Vercel to Claude takes two steps. First, in Elaichi, choose Vercel and paste an API key created in your Vercel account settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself and Vercel is ready to use.

Does Vercel work with ChatGPT and Cursor as well as Claude?

Yes. Once Vercel is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Vercel once and every client you use picks it up.

What can an AI agent actually do with my Vercel data?

With Vercel connected, an agent can list your Vercel teams and projects, look up a single project, create or update a project, and pause one. It can add and remove team members and project members, and view or add environment variables on a project. Vercel has a lot of actions, so short concrete asks, like "pause the staging project" or "who is on the website project", get better results than long paragraphs.

Does connecting Vercel give the AI access to every team and project in my account?

No. A Vercel connection carries exactly the access of the account whose API key was used, so the AI sees the teams, projects and environment variables that account can see in Vercel and nothing beyond that. Elaichi can narrow that access further with restrictions, but it can never widen it.

Can my team share one Vercel connection?

Yes. One person connects Vercel in Elaichi and shares the connection with a team, and nobody else ever handles the Vercel API key. Each teammate still signs in to Elaichi as themselves, so every action taken in Vercel through the shared connection is logged under their own name.

Can I stop an agent from deleting or changing things in Vercel?

Yes. Restrictions in Elaichi work per action, so you can allow reading Vercel projects and members while blocking deleting a project, removing a member, or changing environment variables. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a Vercel connection when someone leaves?

Offboarding a person in Elaichi ends their access to Vercel through Elaichi at once, across every client they used. If the Vercel connection was shared, it keeps working for everyone else on the team. If you disconnect Vercel in Elaichi, it is removed from Claude, ChatGPT, Cursor and every other client in one step.

Put Vercel in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.