Vapi MCP Server
Integrate Vapi APIs with AI assistants through the Model Context Protocol (MCP)
The Vapi Model Context Protocol (MCP) server allows you to integrate with Vapi APIs through tool calling. This enables AI assistants like Claude to directly communicate with Vapi’s services, making it possible to manage assistants, phone numbers, and create calls directly through conversational interfaces.
Looking to use MCP tools with your assistants? See the MCP Tool documentation for integrating external MCP servers with your Vapi assistants.
What is Vapi MCP Server?
Vapi MCP Server is an implementation of the Model Context Protocol that exposes Vapi’s APIs as callable tools. This allows any MCP-compatible client (like Claude Desktop or custom applications using the MCP SDK) to access Vapi functionality, including:
- Listing, creating, and managing Vapi assistants
- Managing phone numbers
- Creating and scheduling outbound calls
- Retrieving call details and status
Supported Actions
The Vapi MCP Server provides the following tools for integration:
Assistant Tools
list_assistants
: Lists all Vapi assistantscreate_assistant
: Creates a new Vapi assistantget_assistant
: Gets a Vapi assistant by ID
Call Tools
list_calls
: Lists all Vapi callscreate_call
: Creates an outbound callget_call
: Gets details of a specific call
Note: The
create_call
action supports scheduling calls for immediate execution or for a future time using the optionalscheduledAt
parameter.
Phone Number Tools
list_phone_numbers
: Lists all Vapi phone numbersget_phone_number
: Gets details of a specific phone number
Setup Options
There are two primary ways to connect to the Vapi MCP Server:
- Local Setup: Run the MCP server locally for development or testing
- Remote SSE Connection: Connect to Vapi’s hosted MCP server via Server-Sent Events (SSE)
Claude Desktop Setup
The easiest way to get started with Vapi MCP Server is through Claude Desktop. This allows you to interact with Vapi services directly through conversations with Claude.
Prerequisites
- Claude Desktop application installed
- Vapi API key (get it from the Vapi dashboard)
Configuration Steps
- Open Claude Desktop and press
CMD + ,
(Mac) to go toSettings
- Click on the
Developer
tab - Click on the
Edit Config
button - This will open the
claude_desktop_config.json
file in your file explorer - Add the following configuration to the file:
- Replace
<your_vapi_token>
with your actual Vapi API key - Save the file and restart Claude Desktop
Example Usage with Claude Desktop
After configuring Claude Desktop with the Vapi MCP server, you can ask Claude to help with Vapi-related tasks.
Example 1: Request an immediate call
Example 2: Schedule a future call
Example 3: Manage assistants
Remote SSE Connection
For production use or if you prefer not to run a local server, you can connect to Vapi’s hosted MCP server via Server-Sent Events (SSE) Transport.
Connection Details
- SSE Endpoint:
https://mcp.vapi.ai/sse
- Authentication: Include your Vapi API key as a bearer token in the request headers
- Example header:
Authorization: Bearer your_vapi_api_key_here
- Example header:
This connection allows you to access Vapi’s functionality remotely without running a local server.
Custom MCP Client Integration
If you’re building a custom application that needs to communicate with Vapi, you can use any MCP-compatible client SDK.
Available SDKs
The Model Context Protocol supports clients in multiple languages:
Integration Steps
- Install the MCP client SDK for your language of choice
- Configure the client to connect to the Vapi MCP Server (either locally or via SSE)
- Query the server for available tools
- Use the tools in your application logic
Here’s an example using the Node.js SDK with SSE transport:
This code shows how to:
- Connect to the Vapi MCP Server using SSE transport
- List available tools
- List your existing assistants
- List your phone numbers
- Create an outbound call using your first assistant and phone number
You can run this code by saving it as a script and executing it with Node.js:
For more detailed examples and complete client implementations, refer to the MCP Client Quickstart.