Vapi MCP Server

Vapi MCP Server is an MCP server that connects AI assistants directly to Vapi's voice AI platform using standardized function calls. Designed for software developers, conversational AI engineers, and automation specialists, the server exposes programmatic interfaces for managing telephony services and speech agents. Users can deploy it locally via stdio or connect to Vapi's hosted remote endpoint over streamable HTTP. Through this server, AI agents can inspect, create, and modify voice assistants, manage assigned phone numbers, and configure function-calling tools that integrate external APIs into voice interactions. In addition, the integration allows connected language models to trigger immediate outbound telephone calls or schedule future calls, complete with custom variable parameters such as customer names or appointment times. By surfacing Vapi API capabilities as Model Context Protocol tools, it enables automated, hands-free management of end-to-end voice telephony workflows directly inside MCP-compatible desktop and terminal clients.

Category: Communication & Messaging

Tags: automation, speech, telephony, voice

Visit Vapi MCP Server

How to install and configure Vapi MCP Server

Follow these steps to set up Vapi MCP Server: 1. Obtain an API token from your Vapi dashboard. 2. Configure your MCP client to run the local stdio package or connect to the hosted remote server. 3. For a local stdio configuration in Claude Desktop, edit your configuration file and add the server specification: json { "mcpServers": { "vapi": { "command": "npx", "args": ["-y", "@vapi-ai/mcp-server"], "env": { "VAPI_TOKEN": "<your_vapi_token>" } } } } 4. If using Claude Code via CLI, run: bash claude mcp add -e VAPI_TOKEN=your_vapi_token vapi -- npx -y @vapi-ai/mcp-server 5. Alternatively, connect remote-capable clients directly to https://mcp.vapi.ai/mcp using the HTTP header Authorization: Bearer your_vapi_api_key_here.

What you can do with Vapi MCP Server

• Creating and configuring new Vapi voice assistants by defining specific system prompts, models, and response parameters directly through an AI chat interface. - Initiating immediate outbound telephone calls to customer phone numbers with custom variable overrides like reminder dates, times, and customer details. - Scheduling future automated calls by supplying designated timestamps, assistant identifiers, and recipient phone numbers to the call scheduling tool. - Querying call history and retrieving execution logs or call details to diagnose call outcomes and monitor telephony interaction performance. - Registering custom external API tools within Vapi assistants to allow voice agents to execute function calls during live phone conversations.

Key facts

• https://github.com/VapiAI/mcp-server
• Communication & Messaging, Design, Media & Creative
• automation, speech, telephony, voice

Part of MCP Servers

How do I install Vapi MCP Server?

You can install and run Vapi MCP Server without manual cloning by running npx with the @vapi-ai/mcp-server package in your client configuration. Alternatively, you can connect directly to Vapi's hosted remote server endpoint at https://mcp.vapi.ai/mcp using a Bearer token authorization header containing your Vapi API key.

What can Vapi MCP Server do?

The server allows AI agents to interact with Vapi voice services. It provides tools to list, create, retrieve, and update voice assistants; initiate or schedule outbound phone calls; inspect call history logs; inspect assigned phone numbers; and define custom function-calling tools for live telephone workflows.

Which MCP clients work with Vapi MCP Server?

The server works with any client supporting the Model Context Protocol over stdio or Streamable HTTP. Tested clients include Claude Desktop and Claude Code CLI. Other MCP-compliant development environments and agents capable of configuring external commands or remote endpoints can also connect.

What credentials are required to use Vapi MCP Server?

You need a valid Vapi API token generated from the Vapi dashboard. This token must be passed as the VAPI_TOKEN environment variable for local stdio setups or provided as an Authorization Bearer header when connecting to the hosted remote server.