Skip to main content
Glama

mcp-vapi

MCP server for Vapi, lets Claude Code, Cursor, Windsurf, and any MCP-compatible AI client manage your voice assistants, fire outbound calls, and inspect call history directly from your AI coding environment.

No more copy-pasting assistant IDs from the dashboard. Just ask Claude.

npm version License: MIT


What You Can Do

Once connected, your AI client can:

  • List, create, update, delete assistants: iterate on prompts without touching the dashboard

  • Fire outbound calls: trigger calls to any number with any assistant

  • Pull call transcripts: get the full transcript + recording URL of any call

  • Manage phone numbers: list your Vapi numbers and grab their IDs

  • Work with squads: create and manage multi-assistant handoff flows

Available Tools

Tool

Description

vapi_list_assistants

List all assistants in your account

vapi_get_assistant

Get full config of a specific assistant

vapi_create_assistant

Create a new voice assistant

vapi_update_assistant

Update an assistant (partial update)

vapi_delete_assistant

Delete an assistant

vapi_create_call

Fire an outbound call

vapi_list_calls

List calls with filters

vapi_get_call

Get call details, transcript, recording

vapi_end_call

Force-end an active call

vapi_list_phone_numbers

List your Vapi phone numbers

vapi_get_phone_number

Get a specific phone number

vapi_list_squads

List all squads

vapi_get_squad

Get squad details

vapi_create_squad

Create a multi-assistant squad

vapi_update_squad

Update a squad

vapi_delete_squad

Delete a squad


Related MCP server: Smallest MCP Server

Setup

1. Get Your Vapi API Key

  1. Go to dashboard.vapi.ai

  2. Click your account avatar → API Keys

  3. Copy your Private Key

Use the private key, not the public key. The public key is for client-side SDKs.

2. Add to Claude Code

claude mcp add vapi -e VAPI_API_KEY=your_key_here -- npx -y mcp-vapi

That's it. Restart Claude Code and the Vapi tools will be available.

3. Add to Claude Desktop

Open your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this to the mcpServers section:

{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["-y", "mcp-vapi"],
      "env": {
        "VAPI_API_KEY": "your_key_here"
      }
    }
  }
}

Restart Claude Desktop.

4. Add to Cursor / Windsurf

In your MCP settings file, add:

{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["-y", "mcp-vapi"],
      "env": {
        "VAPI_API_KEY": "your_key_here"
      }
    }
  }
}

Usage Examples

Once connected, just talk to your AI:

"List all my Vapi assistants"

Claude calls vapi_list_assistants and returns the names + IDs

"Create a new assistant called 'HVAC Receptionist' with this system prompt: [paste prompt]"

Claude calls vapi_create_assistant with the right params

"Fire a test call to +14155550100 using assistant ID abc123 from phone number xyz789"

Claude calls vapi_create_call with your phone number ID, the customer number, and assistant ID

"Get the transcript from call ID def456"

Claude calls vapi_get_call and returns the full transcript + recording URL

"Update the system prompt on assistant abc123 to [new prompt]"

Claude calls vapi_update_assistant with just the systemPrompt field


Tips

You still need a Vapi phone number to make outbound calls. Buy one at dashboard.vapi.ai → Phone Numbers, then list them with vapi_list_phone_numbers to grab the ID.

E.164 format for phone numbers. Always +[country code][number], no dashes or spaces. +14155550100 ✅, 415-555-0100 ❌.

Metadata is your friend. Pass a metadata object when creating a call, it comes back on every webhook event so you can link calls to CRM records, campaigns, or anything else.

assistantOverrides is super useful. You don't need a separate assistant per lead. Create one assistant and pass per-call overrides like firstMessage, variableValues, or serverUrl when you create the call.

Pagination is timestamp-based. Vapi doesn't use page numbers, use createdAtGt/createdAtLt to paginate through large result sets.


Local Development

git clone https://github.com/adhirajhangal/mcp-vapi
cd mcp-vapi
npm install
npm run build

# test it
VAPI_API_KEY=your_key node dist/index.js

To use your local build in Claude Code:

claude mcp add vapi-local -e VAPI_API_KEY=your_key -- node /path/to/mcp-vapi/dist/index.js

Resources


License

MIT

Available Tools

16 tools
vapi_create_assistantCreate Vapi AssistantC

Create a new Vapi voice assistant. You can set its name, first message, system prompt, LLM model, voice, and more.

Inputs: name (required), firstMessage, systemPrompt, modelProvider, +5 more.

vapi_create_callCreate Outbound CallB

Fire an outbound call using a Vapi assistant. Needs your Vapi phone number ID and the customer's number in E.164 format (+14155550100).

Inputs: phoneNumberId (required), customerNumber (required), customerName, assistantId, +4 more.

vapi_create_squadCreate Vapi SquadB

Create a squad of assistants that can hand off to each other on a call. Great for receptionist → qualifier → closer flows.

Inputs: name (required), members (required).

vapi_delete_assistantDelete Vapi AssistantA

Permanently delete a Vapi assistant. This cannot be undone.

Inputs: assistantId (required).

vapi_delete_squadDelete Vapi SquadC

Permanently delete a squad.

Inputs: squadId (required).

vapi_end_callEnd Active CallA

Force-end an active Vapi call. Useful if a call gets stuck or needs to be terminated from a workflow.

Inputs: callId (required).

vapi_get_assistantGet Vapi AssistantB

Get full details of a specific Vapi assistant by ID, including its model, voice, and prompt config.

Inputs: assistantId (required).

vapi_get_callGet Vapi CallB

Get full details of a call including transcript, recording URL, cost, end reason, and summary.

Inputs: callId (required).

vapi_get_phone_numberGet Vapi Phone NumberC

Get details of a specific Vapi phone number.

Inputs: phoneNumberId (required).

vapi_get_squadGet Vapi SquadB

Get details of a specific squad including its member assistants.

Inputs: squadId (required).

vapi_list_assistantsList Vapi AssistantsB

List all voice assistants in your Vapi account. Returns IDs, names, and config.

Inputs: limit, createdAtGt, createdAtLt.

vapi_list_callsList Vapi CallsC

List calls with optional filters. Returns call IDs, status, cost, and basic info.

Inputs: limit, assistantId, phoneNumberId, createdAtGt, +1 more.

vapi_list_phone_numbersList Vapi Phone NumbersA

List all phone numbers in your Vapi account. Use the IDs when creating calls.

Inputs: limit.

vapi_list_squadsList Vapi SquadsB

List all squads in your account. Squads are groups of assistants that hand off to each other.

Inputs: limit.

vapi_update_assistantUpdate Vapi AssistantC

Update an existing assistant (partial update — only send the fields you want to change).

Inputs: assistantId (required), name, firstMessage, systemPrompt, +2 more.

vapi_update_squadUpdate Vapi SquadC

Update a squad — rename it or change its members.

Inputs: squadId (required), name, members.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources (assistants, calls, squads, phone numbers) and actions (create, get, list, update, delete, end). No overlap exists; for example, vapi_create_assistant and vapi_update_assistant are clearly differentiated by their operations on the same resource.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the prefix 'vapi_' (e.g., vapi_create_assistant, vapi_get_call, vapi_list_squads). The naming is uniform across all 16 tools, using snake_case and clear action-resource pairs without any deviations.

    Tool Count5/5

    With 16 tools, the server is well-scoped for managing Vapi's core entities (assistants, calls, squads, phone numbers). Each tool serves a specific CRUD or operational function, and the count aligns with the domain's complexity without being excessive or insufficient.

    Completeness5/5

    The tool set provides complete CRUD and lifecycle coverage for all key resources: assistants, calls, squads, and phone numbers. It includes creation, retrieval, listing, updating, and deletion, plus operational tools like vapi_end_call, ensuring no gaps for agent workflows in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      VoiceLayer MCP server enables AI coding assistants to speak and hear via local, on-device speech-to-text and text-to-speech, with no cloud dependencies.
      1,520 npm
      1
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      An MCP server that enables AI assistants to interact with the VoIPbin CPaaS platform, exposing tools for managing calls, flows, messaging, conferencing, and more.
      66
      1
      MIT