Hosting

local or remote

Transport

stdio

Endpoint

https://mcp.vapi.ai/mcp

Authentication

Vapi API key; local stdio uses VAPI_TOKEN and the hosted endpoint uses Authorization: Bearer.

Requirements

• Vapi dashboard API key
• Node.js/npx for local install

Setup steps

1. Local: configure command npx args [-y, @vapi-ai/mcp-server] and env VAPI_TOKEN=<VAPI_API_KEY>.
2. Remote: connect to https://mcp.vapi.ai/mcp and send Authorization: Bearer <VAPI_API_KEY>.
3. Claude Code example: `claude mcp add -e VAPI_TOKEN=<VAPI_API_KEY> vapi -- npx -y @vapi-ai/mcp-server`.

The current official Vapi MCP server README lists 13 tools across assistants, calls, phone numbers, and custom tools. This updates the earlier seven-tool subset; no API calls were made.

• list_assistants

  List all assistants

  01
• get_assistant

  Get an assistant by ID

  02
• create_assistant

  Create a new assistant

  03
• update_assistant

  Update an assistant

  04
• list_calls

  List call history

  05
• get_call

  Get details for a call

  06
• create_call

  Start an outbound call immediately or schedule it

  07
• list_phone_numbers

  List phone numbers

  08
• get_phone_number

  Get phone number details

  09
• list_tools

  List custom tools

  10
• get_tool

  Get tool details

  11
• create_tool

  Create a tool for API integration

  12
• update_tool

  Update a tool

  13

• Creating calls initiates or schedules outbound calls. Creating or updating assistants and tools changes account configuration. The remote endpoint requires an API key.

• official repository tool reference

  Current VapiAI README documents hosted and stdio setup and enumerates 13 exact tools across assistants, calls, phone numbers, and custom tools.

• official product documentation

  Vapi docs describe API-key authentication and representative assistant/call tools.

Documentation checked 2026-10-28T14:10:00.000Z. Connection has not been runtime tested.