Vapi MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAPI_TOKEN | Yes | Your Vapi API key from the Vapi dashboard |
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 |
|---|---|
| list_assistantsA | Lists all Vapi assistants |
| create_assistantB | Creates a new Vapi assistant |
| get_assistantB | Gets a Vapi assistant by ID |
| update_assistantC | Updates an existing Vapi assistant |
| list_callsB | Lists all Vapi calls |
| create_callC | Creates a outbound call |
| get_callB | Gets details of a specific call |
| list_phone_numbersA | Lists all Vapi phone numbers |
| get_phone_numberC | Gets details of a specific phone number |
| list_toolsA | Lists all Vapi tools |
| get_toolB | Gets details of a specific tool |
| create_toolC | Creates a new Vapi tool |
| update_toolC | Updates an existing Vapi tool |
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 13 tools
Each tool targets a distinct resource and action: assistants, calls, phone numbers, and tools are clearly separated, with list/get/create/update operations uniquely identified. There is no functional overlap between any tools.
All 13 tools follow a consistent verb_noun pattern with lowercase and underscores, such as list_assistants, create_call, get_phone_number. The convention is uniform across all resources.
With 13 tools spanning three core resource types, the count is well within the optimal range. Each tool serves a distinct purpose with no redundancy.
Assistants and tools have full CRUD except delete operations, while phone numbers lack create/update/delete and calls lack update/delete. These are minor gaps but may reflect API constraints; core read and update workflows are covered.