What it does
Vapi MCP Server connects Claude to Vapi's voice infrastructure for building and managing AI voice assistants and phone agents. It exposes 13 tools covering assistant creation and management, immediate and scheduled outbound calls, phone number provisioning, and custom API integration via function calling. Assistants support dynamic variable interpolation—pass customer names, dates, or custom fields to parameterize behavior during voice interactions.
Who it's for
Backend engineers and product teams building voice applications: appointment reminders, customer support automation, outbound calling systems. Developers wanting to prototype and deploy voice workflows inside Claude Code without switching to a web dashboard.
Common use cases
- Create voice assistants for appointment scheduling, support triage, or domain-specific conversations
- Make outbound calls with contextual data (customer name, appointment details, callback numbers) automatically populated
- Provision and manage phone numbers for inbound and outbound calling at scale
- Integrate custom APIs and business logic via function calling, triggered from assistant prompts
Setup pitfalls
- OAuth requires browser sign-in on first use; Claude Code automates this via
claude mcp add, but other MCP clients must handle the redirect explicitly - API key authentication needs
VAPI_TOKENenvironment variable; there is no built-in fallback if missing or revoked - The remote MCP server at https://mcp.vapi.ai/mcp requires
Authorization: Bearer <token>headers; HTTP streaming is recommended over the deprecated SSE endpoint - No CI is configured and the last commit was 20 days ago—verify compatibility before production use