vapi-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAPI_API_KEY | Yes | Your Vapi private API key (Bearer token). Found in Organization Settings > API Keys at dashboard.vapi.ai. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vapi_list_assistantsA | List all Vapi assistants |
| vapi_get_assistantC | Get a specific Vapi assistant |
| vapi_create_assistantC | Create a new Vapi assistant |
| vapi_update_assistantC | Update an existing Vapi assistant |
| vapi_delete_assistantC | Delete a Vapi assistant |
| vapi_list_callsB | List all Vapi calls |
| vapi_get_callC | Get a specific Vapi call |
| vapi_create_callC | Initiate a new Vapi call |
| vapi_end_callC | End an active Vapi call |
| vapi_evaluate_callC | Evaluate a Vapi call |
| vapi_list_phone_numbersB | List all Vapi phone numbers |
| vapi_get_phone_numberB | Get a specific Vapi phone number |
| vapi_buy_phone_numberC | Buy a new Vapi phone number |
| vapi_import_phone_numberC | Import a phone number to Vapi |
| vapi_list_toolsA | List all Vapi tools |
| vapi_get_toolC | Get a specific Vapi tool |
| vapi_create_toolC | Create a new Vapi tool |
| vapi_update_toolC | Update an existing Vapi tool |
| vapi_delete_toolC | Delete a Vapi tool |
| vapi_list_squadsA | List all Vapi squads |
| vapi_get_squadC | Get a specific Vapi squad |
| vapi_create_squadC | Create a new Vapi squad |
| vapi_update_squadC | Update an existing Vapi squad |
| vapi_delete_squadC | Delete a Vapi squad |
| vapi_get_analyticsD | Get Vapi analytics |
| vapi_generate_workflowD | Generate a new Vapi workflow using AI |
| vapi_chatC | Send a message to an assistant or continue a chat session |
| vapi_list_sessionsA | List all Vapi chat sessions |
| vapi_get_sessionC | Get a specific Vapi chat session |
| vapi_create_sessionC | Create a new Vapi chat session |
| vapi_delete_sessionC | Delete a Vapi chat session |
| vapi_create_support_ticketC | File a support ticket with Vapi |
| vapi_get_call_artifactsB | Extract deep diagnostic artifacts from a completed call |
| vapi_get_campaign_analyticsB | Get simplified campaign analytics to fetch the total call count |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
All tools target distinct resources (assistant, call, phone number, session, squad, tool, etc.) with unique actions. No two tools overlap in purpose; even similar ones like vapi_evaluate_call and vapi_get_call_artifacts are clearly differentiated by description.
All tools follow a consistent pattern: vapi_verb_noun (e.g., vapi_create_assistant, vapi_list_phone_numbers). The prefix 'vapi_' is used uniformly, and verbs are predictable (create, delete, get, list, update, etc.).
With 34 tools, the server is well above the typical 3-15 range and even beyond the 16-25 borderline. While the tools are organized, the count feels excessive for a single MCP server, likely overwhelming agents.
The tool surface covers most core operations for assistants, calls, squads, and tools (CRUD-like), but phone numbers and sessions are missing update and delete operations. Additionally, support tickets only have a create tool. These gaps are notable but not severely blocking.