Hey there! This is a custom Model Context Protocol (MCP) server designed specifically for the Vapi Voice AI platform. I built this to bridge the gap between AI models and Vapi's infrastructure, allowing agents to actually manage voice bots and phone calls instead of just talking about them.
This project was built and is maintained by Ageborn Dev.
Basically, if you're using Claude Desktop or any other MCP-compatible client, you can plug this server in and give your AI "admin rights" over your Vapi dashboard. It can create assistants, trigger outbound calls, buy phone numbers, and check your analytics directly through the chat interface.
Getting this running is pretty straightforward, but you need the right keys.
Vapi provides two types of keys in your dashboard. It's important to use the right one:
-
Private API Key (Bearer Token):
- What it's for: Full server-side access. This is what this MCP server needs to manage your assistants, initiate calls, and pull analytics.
- Where to find it: Go to dashboard.vapi.ai, click on Organization Settings, and look for the API Keys tab. You'll see your "Private Key" or "Bearer Token" there.
- Security: Never share this key. It grants total control over your account.
-
Public Key:
- What it's for: Used strictly for client-side integrations (like embedding a voice widget on a website or in a mobile app).
- Usage: You do not need this for the MCP server.
-
Clone and Install:
npm install
-
Configure Your Keys:
Depending on your system, here is how you make sure the server sees your API key:
-
Windows (PowerShell):
$env:VAPI_API_KEY = "your_private_key_here" # To make it permanent, add it to your System Environment Variables via Settings.
-
Mac / Linux (Terminal):
export VAPI_API_KEY="your_private_key_here" # Add this to your ~/.zshrc or ~/.bashrc to keep it after restart.
Alternatively, just create a
.envfile in the root directory:cp .env.example .env
-
-
Build & Start:
npm run build npm start
I've packed this server with over 20 tools. Here’s the breakdown of what your AI can actually do:
- Assistants: Full CRUD (Create, Read, Update, Delete) support for your voice bots.
- Calls: You can start calls, end them, and get full transcripts or evaluations.
- Phone Numbers: Buy new numbers or import existing ones from Twilio/Vonage without leaving the chat.
- Knowledge & Tools: Manage the "brains" and webhooks that power your assistants.
- Squads: Handle multi-assistant handoffs and complex architectures.
- Data: Pull analytics, cost reports, and logs for debugging.
To make this server available to the agent in your Antigravity environment, follow these exact steps:
The configuration is managed globally within the Antigravity IDE.
- In the Antigravity editor, go to the Agent Pane (typically top right).
- Click the Three-Dot Menu (Additional Options).
- Select MCP Servers -> Manage MCP Servers.
- Click View raw config. This will open the official
mcp_config.jsonfile in your editor.
Add the following entry inside the "mcpServers" object. Make sure to use absolute paths.
{
"mcpServers": {
"vapi": {
"command": "node",
"args": ["path of the instalation/vapi-mcp-server/build/index.js"],
"env": {
"VAPI_API_KEY": "your_private_api_key_here"
}
}
}
}- Save the
mcp_config.jsonfile. - Go back to the Manage MCP Servers view in the Agent Pane.
- Click the Refresh button.
- The "vapi" server should now appear in the list with all 20+ tools enabled.
Once registered, you can just tell the agent: "List my Vapi assistants" or "Create a call with..." and it will use these tools directly.
Built with Love ❤️ and ☕ by Ageborn Dev