Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Vapi MCP Server for Claude

Build and manage AI voice assistants and phone agents from Claude — create assistants, make outbound calls, manage phone numbers, and configure custom tools — with the official Vapi Model Context Protocol server backed by the Vapi API.

by Vapi·added 2026-06-18·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • `vapi_create_call` starts a real outbound phone call immediately — confirm the recipient number before invoking.
  • `vapi_buy_phone_number` purchases a real phone number and incurs billing charges on your Vapi account.
  • Write operations (create, update, delete) for assistants, calls, and phone numbers are irreversible in some cases — review before confirming.

Privacy notes

  • Assistant configurations, call history, phone numbers, and custom tool definitions from your Vapi account are surfaced in Claude's context.
  • OAuth authenticates without storing credentials; if using an API key, store it in Claude Code's MCP config rather than shell history.

Prerequisites

  • A Vapi account — authenticate via browser OAuth on first use (no API key copy-paste required).
  • Node.js (v18+) with `npx` available, and an MCP client such as Claude Code or Claude Desktop.
  • To use an API key instead of OAuth, get one from the Vapi dashboard under API Keys.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["-y", "@vapi-ai/mcp-server"]
    }
  }
}

About this resource

Overview

The Vapi MCP Server is the official Model Context Protocol server from Vapi. It gives Claude direct access to your Vapi account — voice assistants, outbound calls, phone numbers, and custom tools — so you can build and manage AI phone agents using natural language. Authentication is via browser OAuth on first use (no API key required), or optionally via a VAPI_TOKEN environment variable. Licensed under MIT.

A hosted remote endpoint is also available at https://mcp.vapi.ai/mcp via mcp-remote.

Key capabilities

  • Voice assistants — create, configure, update, and delete AI voice assistants with custom voices, prompts, and conversation flows.
  • Outbound calls — start immediate or scheduled outbound phone calls via vapi_create_call.
  • Phone numbers — browse, purchase, configure, and release phone numbers.
  • Custom tools — register API integrations and custom function tools for assistants to invoke.
  • OAuth login — sign in and out via browser without touching API keys.

Tools

Tool Purpose
vapi_list_assistants / vapi_get_assistant Browse assistant configurations
vapi_create_assistant / vapi_update_assistant / vapi_delete_assistant Manage assistants
vapi_list_calls / vapi_get_call Browse call history and details
vapi_create_call Start an outbound call (immediate or scheduled)
vapi_list_phone_numbers / vapi_buy_phone_number Manage phone numbers
vapi_list_tools / vapi_create_tool / vapi_update_tool Manage custom API tools
vapi_login / vapi_logout Manage OAuth session

How it compares

Server Voice assistants Outbound calls Phone numbers Custom tools Auth
Vapi MCP Full CRUD Yes Buy + manage Full CRUD OAuth / API key
Twilio MCP No Yes Buy + manage No API key
ElevenLabs MCP Voice only No No No API key
Bland AI MCP Limited Yes Limited No API key

Vapi is the only voice AI MCP server that provides full assistant lifecycle management (create, configure, deploy), outbound call control, and custom tool registration in a single integration.

Installation

Claude Code (OAuth — recommended)

claude mcp add vapi -- npx -y @vapi-ai/mcp-server

On first use, Claude Code will open a browser window for Vapi OAuth sign-in — no API key required.

Claude Code (API key)

claude mcp add vapi -e VAPI_TOKEN=your-api-key -- npx -y @vapi-ai/mcp-server

Claude Desktop

{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["-y", "@vapi-ai/mcp-server"],
      "env": {
        "VAPI_TOKEN": "your-vapi-api-key"
      }
    }
  }
}

Remote (hosted) endpoint

{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.vapi.ai/mcp"]
    }
  }
}

Requirements

  • A Vapi account (sign up free at vapi.ai).
  • Node.js v18+ with npx.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • OAuth flow stores credentials securely without API key exposure.
  • vapi_create_call triggers real phone calls — confirm recipient before invoking.
  • vapi_buy_phone_number incurs real charges — review before confirming.

Source Verification Notes

Verified on 2026-06-18:

  • Official GitHub repository VapiAI/mcp-server (MIT, 55+ stars) documents the @vapi-ai/mcp-server npm package, OAuth flow, VAPI_TOKEN env var, hosted endpoint at https://mcp.vapi.ai/mcp, and all 20 tools across assistants, calls, phone numbers, and custom tools.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the stdio connector setup pattern used above.
#vapi#voice-ai#phone-agents#assistants#telephony#ai-agents#voice

Source citations

Add this badge to your README

Show that Vapi MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/vapi-mcp-server.svg)](https://heyclau.de/entry/mcp/vapi-mcp-server)

How it compares

Vapi MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldVapi MCP Server for Claude

Build and manage AI voice assistants and phone agents from Claude — create assistants, make outbound calls, manage phone numbers, and configure custom tools — with the official Vapi Model Context Protocol server backed by the Vapi API.

Open dossier 		Axiom MCP Server for Claude

Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server.

Open dossier 		Brex MCP Server for Claude

Manage your Brex corporate card and banking account from Claude — expenses, cards, transactions, users, bills, vendors, travel bookings, and spend analytics — with the official Brex remote MCP server.

Open dossier 		LaunchDarkly MCP Server for Claude

Manage LaunchDarkly feature flags, AI configs, environments, and audit logs from Claude — with the official LaunchDarkly Model Context Protocol server backed by the LaunchDarkly REST API.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorVapiAxiom, Inc.BrexLaunchDarkly
Added2026-06-182026-06-182026-06-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓`vapi_create_call` starts a real outbound phone call immediately — confirm the recipient number before invoking. `vapi_buy_phone_number` purchases a real phone number and incurs billing charges on your Vapi account. Write operations (create, update, delete) for assistants, calls, and phone numbers are irreversible in some cases — review before confirming.✓The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming. APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota.✓Each tool requires specific Brex user capabilities — access is constrained by your existing Brex account permissions and team policies. This MCP server provides read and write access to financial data including expenses, cards, and transactions; confirm any write operations before approving. API key auth should use a token scoped to the minimum required permissions; rotate keys regularly from Settings → Developer.✓Feature flag operations include create, update (patch), and delete — changes affect live targeting rules for all users in the environment. Audit log and code reference reads are non-destructive, but flag patch and delete operations are irreversible and will affect production traffic immediately. Scope the API key to the minimum required permissions (read-only for analysis workflows, write only for flag management workflows).
Privacy notes✓Assistant configurations, call history, phone numbers, and custom tool definitions from your Vapi account are surfaced in Claude's context. OAuth authenticates without storing credentials; if using an API key, store it in Claude Code's MCP config rather than shell history.✓Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.✓Expense details, card data, banking transactions, user profiles, and vendor information from your Brex workspace are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration.✓Feature flag definitions, targeting rules, user segments, AI config prompts, environment configurations, and audit log entries from your LaunchDarkly project are surfaced in Claude's context. Your API key is passed as a CLI argument — store it in Claude Code's MCP config rather than in shell history; rotate keys from the LaunchDarkly Authorization page.
Prerequisites
  • A Vapi account — authenticate via browser OAuth on first use (no API key copy-paste required).
  • Node.js (v18+) with `npx` available, and an MCP client such as Claude Code or Claude Desktop.
  • To use an API key instead of OAuth, get one from the Vapi dashboard under API Keys.
  • An Axiom account — authenticate via OAuth when prompted in Claude Code, or generate an API token in Axiom settings.
  • An MCP client such as Claude Code or Claude Desktop.
  • A Brex account — authenticate via OAuth (recommended) when prompted, or generate a Bearer API key in Settings → Developer.
  • Permissions in your Brex workspace aligned with the data you need (expenses, cards, banking).
  • An MCP client such as Claude Code or Claude Desktop.
  • A LaunchDarkly account and an API key from the LaunchDarkly Authorization page (Settings → Authorization → API Keys).
  • Node.js (v18+) with `npx` available, and an MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add vapi -- npx -y @vapi-ai/mcp-server
claude mcp add --transport http axiom https://mcp.axiom.co/mcp
claude mcp add --transport http brex https://api.brex.com/mcp
claude mcp add launchdarkly -- npx -y --package @launchdarkly/mcp-server -- mcp start --api-key YOUR_API_KEY
Config
{
  "mcpServers": {
    "vapi": {
      "command": "npx",
      "args": ["-y", "@vapi-ai/mcp-server"],
      "env": {
        "VAPI_TOKEN": "your-vapi-api-key"
      }
    }
  }
}
{
  "mcpServers": {
    "axiom": {
      "type": "http",
      "url": "https://mcp.axiom.co/mcp"
    }
  }
}
{
  "mcpServers": {
    "brex": {
      "type": "http",
      "url": "https://api.brex.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "LaunchDarkly": {
      "command": "npx",
      "args": ["-y", "--package", "@launchdarkly/mcp-server", "--", "mcp", "start", "--api-key", "YOUR_API_KEY"]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.