by VapiAI
Vapi MCP Server enables Vapi integration via the Model Context Protocol, providing function-calling AI API access so mod
Connects AI models to Vapi's voice assistant and phone agent APIs through the Model Context Protocol. Lets you build and manage AI-powered voice applications directly from Claude or other MCP-compatible tools.
Vapi MCP Server is an official MCP server published by VapiAI that provides AI assistants with tools and capabilities via the Model Context Protocol. Vapi MCP Server enables Vapi integration via the Model Context Protocol, providing function-calling AI API access so mod It is categorized under communication, ai ml.
You can install Vapi MCP Server in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Vapi MCP Server is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Vapi MCP Server has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Vapi MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Vapi MCP Server reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Vapi MCP Server for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, Vapi MCP Server benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Vapi MCP Server is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We wired Vapi MCP Server into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: Vapi MCP Server surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Useful MCP listing: Vapi MCP Server is the kind of server we cite when onboarding engineers to host + tool permissions.
We evaluated Vapi MCP Server against two servers with overlapping tools; this profile had the clearer scope statement.
showing 1-10 of 74
Build AI voice assistants and phone agents with Vapi using the Model Context Protocol.
<a href="https://glama.ai/mcp/servers/@VapiAI/mcp-server"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@VapiAI/mcp-server/badge" alt="Vapi Server MCP server" /> </a>The easiest way to get started. No API key needed - authenticate via browser on first use.
claude mcp add vapi -- npx -y @vapi-ai/mcp-server
The Vapi skill helps Claude guide you through building voice assistants:
mkdir -p ~/.claude/skills/vapi
curl -o ~/.claude/skills/vapi/SKILL.md https://raw.githubusercontent.com/VapiAI/mcp-server/main/skill/SKILL.md
After restarting, use /vapi or ask Claude to help build a voice assistant. On first use, you'll be prompted to sign in via browser - no API key copy-paste needed.
{
"mcpServers": {
"vapi": {
"command": "npx",
"args": ["-y", "@vapi-ai/mcp-server"]
}
}
}
If you prefer to use an API key directly, get one from the Vapi dashboard:
{
"mcpServers": {
"vapi": {
"command": "npx",
"args": ["-y", "@vapi-ai/mcp-server"],
"env": {
"VAPI_TOKEN": "<your_vapi_token>"
}
}
}
}
Connect to Vapi's hosted MCP server:
{
"mcpServers": {
"vapi": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.vapi.ai/mcp",
"--header",
"Authorization: Bearer ${VAPI_TOKEN}"
],
"env": {
"VAPI_TOKEN": "<your_vapi_token>"
}
}
}
}
Ask Claude:
I want to build a voice assistant that can schedule appointments
Call +1234567890 using my appointment reminder assistant with these details:
- Customer name: Sarah Johnson
- Appointment date: March 25th
- Appointment time: 2:30 PM
Schedule a call with my support assistant for next Tuesday at 3:00 PM to +1555123456
The create_call action supports passing dynamic variables through assistantOverrides.variableValues. Use double curly braces in your assistant's prompts: {{variableName}}.
Hello {{customerName}}, this is a reminder about your appointment on {{appointmentDate}} at {{appointmentTime}} with {{doctorName}}.
These are automatically available (no need to pass):
{{now}} - Current date and time (UTC){{date}} - Current date (UTC){{time}} - Current time (UTC){{month}} - Current month (UTC){{day}} - Current day of month (UTC){{year}} - Current year (UTC){{customer.number}} - Customer's phone numberSee Vapi documentation for advanced date/time formatting.
Connect to Vapi's hosted MCP server from any MCP client:
https://mcp.vapi.ai/mcpAuthorization: Bearer your_vapi_api_key_herehttps://mcp.vapi.ai/sseAuthorization: Bearer your_vapi_api_key_here| Tool | Description |
|---|---|
vapi_list_assistants | List all assistants |
vapi_get_assistant | Get assistant by ID |
vapi_create_assistant | Create new assistant |
vapi_update_assistant | Update assistant |
vapi_delete_assistant | Delete assistant |
| Tool | Description |
|---|---|
vapi_list_calls | List call history |
vapi_get_call | Get call details |
vapi_create_call | Start outbound call (immediate or scheduled) |
| Tool | Description |
|---|---|
vapi_list_phone_numbers | List phone numbers |
vapi_get_phone_number | Get phone number details |
vapi_buy_phone_number | Purchase new number |
vapi_update_phone_number | Update number settings |
vapi_delete_phone_number | Release number |
| Tool | Description |
|---|---|
vapi_list_tools | List custom tools |
vapi_get_tool | Get tool details |
vapi_create_tool | Create tool for API integration |
vapi_update_tool | Update tool |
vapi_delete_tool | Delete tool |
| Tool | Description |
|---|---|
vapi_login | Start OAuth flow |
vapi_logout | Log out and clear credentials |
# Install dependencies
npm install
# Build
npm run build
# Test with MCP inspector
npm run inspector
{
"mcpServers": {
"vapi-local": {
"command": "node",
"args": ["<path>/dist/index.js"],
"env": {
"VAPI_TOKEN": "<your_vapi_token>"
}
}
}
}
# Unit tests (mocked)
npm run test:unit
# E2E tests (requires VAPI_TOKEN)
export VAPI_TOKEN=your_token_here
npm run test:e2e
# All tests
npm test
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.