Skip to content

Voice

Vapi MCP connector

Connect Vapi to Claude, ChatGPT, Cursor and any MCP client so your team can review calls, recordings and call logs, and adjust voice assistants in plain language, with every action logged.

  • 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 Vapi to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Vapi once

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

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

  3. Paste a Vapi API key. One person generates a token in Vapi 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.

vapi
Vapi
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 Vapi 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 Vapi 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 Vapi 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 Vapi 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 Vapi through Elaichi

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

  • Support

    Find out why a call went badly

    When a customer complains about a voice assistant, pull up that Vapi call, its log and its recording in one ask and see what was said and where it went wrong.

  • Sales

    Start outbound calls from a lead list

    Hand the agent a list of numbers and the assistant to use, and it places the Vapi calls, then reports back which ones connected.

  • Operations

    Change an assistant's script the same day

    Ask for the greeting, voice or instructions on a Vapi assistant to be updated, and the change is live without opening the dashboard.

  • Quality

    Review yesterday's recordings in one pass

    List the day's Vapi recordings and call logs, have them summarized, and flag the calls where the assistant stumbled or a caller hung up early.

  • Product

    Build a test assistant and add it to a squad

    Create a new Vapi assistant, put it in a squad alongside the current one, and run a few calls to compare how each handles the same request.

  • Marketing

    Check how a calling campaign is doing

    Ask how many Vapi calls a campaign assistant made this week, how long they ran, and which ones ended with the caller asking to be called back.

Try asking

  • “Which Vapi assistants handled the most calls this week?”
  • “Show me yesterday's failed Vapi calls by assistant.”
  • “List every Vapi squad and the assistants inside it.”

See all 86 Vapi tools below

AI tools

Vapi tools for your AI agents

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

See it in Elaichi

What connecting Vapi gets you

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

The agent

Ask about calls, get real answers.

Type a question in plain language and read live Vapi assistants and calls.

  • assistants
  • squads
  • calls
  • phone numbers

Ask Elaichi to work across your apps.

Which Vapi assistants handled the most calls this week?

Show me yesterday's failed Vapi calls by assistant.

List every Vapi squad and the assistants inside it.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect any MCP client to Vapi over OAuth, no SDK, no shared 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

86 Vapi tools ready without custom code.

Assistants, squads and calls come with list, create, update and delete methods.

  • List all Vapi assistants
  • Create a Vapi assistant
  • Get single Vapi assistant by ID
  • Update a Vapi assistant by ID
ElaichiTools
Tool Action Description
List all Vapi assistants List List vapi assistants. Returns: id, createdAt, updatedAt. Supports optional filtering by creation and update timestamps (gt, lt, ge, le variants for both createdAt and updatedAt).
Create a Vapi assistant Create Create a new vapi assistant. Returns: id, createdAt, updatedAt.
Get single Vapi assistant by ID Get Get a single vapi assistant by id. Returns: id, createdAt, updatedAt. Required: id.
Update a Vapi assistant by ID Update Update a vapi assistant by id using a partial payload. Returns: id, createdAt, updatedAt. Required: id.
Delete a Vapi assistant by ID Delete Delete a vapi assistant by id. Returns the deleted assistant object including id, createdAt, updatedAt. Required: id.

Toolboxes

Every team gets its own Vapi toolbox.

Support, sales and engineering each see the Vapi tools their work needs.

  • Support
  • Sales
  • Engineering
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Vapi · inbound calls and assistants

Vapi starter 18 Mar 4, 2026

Sales toolbox

Vapi · outbound calls and squads

9 Mar 2, 2026

Engineering toolbox

Vapi · assistant configuration and phone numbers

24 Feb 27, 2026

Operations toolbox

Vapi · call volume and routing

Vapi starter 6 Feb 19, 2026

Quality toolbox

Vapi · call transcripts and reviews

31 Jan 30, 2026

Marketing toolbox

Vapi · campaign calls and scripts

12 Jan 22, 2026

Shared connections

Teammates use Vapi accounts, never credentials.

See who connected each Vapi account and how many teams and members share it.

  • Support EMEA
  • Sales US
  • Outbound Campaigns
  • Engineering Sandbox
ElaichiConnections
Connection Scope Status Access
VA

Vapi (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
VA

Vapi (Sales US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
VA

Vapi (Outbound Campaigns)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
VA

Vapi (Engineering Sandbox)

Connected by Daniel Ortega

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

Vapi (Quality Review)

Connected by Clara Nowak

Personal • Active Not shared
VA

Vapi (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which Vapi assistant.

Every call records when, who, what happened, type and the resource touched.

  • 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]

Vapi Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Vapi Assistants Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Vapi Assistants 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 fires, a digest ships.

Vapi calls are fetched, grouped, drafted by an agent, approved, then posted back.

Vapi digest

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch assistants

    Vapi

    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

    Vapi

    Queued

Collections and dashboards

Vapi call numbers land before you ask.

Four metrics, 14 days of calls created and a team breakdown, computed on schedule.

Vapi health

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

Live

Assistants

1,284 ↓ 12%

Squads

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Assistants created

Last 14 days

By team

Share of activity

Support EMEA 34%

Sales US 27%

Outbound Campaigns 21%

Engineering Sandbox 18%

FAQ

Frequently asked questions

How do I connect Vapi to Claude?

Connect Vapi in Elaichi first, which asks only for your Vapi API key, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in Vapi and no client ID or secret to generate. Once the endpoint is in place, Claude signs in through Elaichi and your Vapi assistants, calls and recordings are available.

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

Yes. You connect Vapi once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Each client signs in with the same account and sees the same Vapi connection.

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

An agent connected to Vapi can list and look up your assistants, squads, calls, recordings, call logs and chats, place new calls, start chats, and create, update or delete assistants and squads. In practice that means asking for the recording of a specific call, changing an assistant's greeting, or summarizing yesterday's call logs. Because Vapi has many capabilities, short concrete asks such as "show me the calls from today" work better than long instructions.

Does connecting Vapi give the AI everything in my Vapi account?

The AI sees only what the person who signed in can see in Vapi, because every call runs under that person's own access. Elaichi can narrow that further, for example to reading calls and recordings without changing assistants, but it can never widen what Vapi itself allows.

Can my team share one Vapi connection?

Yes. One person connects Vapi with the API key, shares the connection with a team in Elaichi, and nobody else on the team ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who placed a Vapi call or changed an assistant.

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

Yes. Restrictions in Elaichi apply per action, so you can allow listing Vapi calls and recordings while blocking the deletion of assistants, squads or calls. A blocked action is never shown to Claude, ChatGPT or any other client, so no prompt can reach it.

What happens to a Vapi connection when someone leaves?

Offboarding the person in Elaichi ends their access to Vapi through every client at once. If they connected a shared Vapi account, the connection keeps working for everyone else on the team. Disconnecting Vapi once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Put Vapi in front of your team

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