Skip to navigation

Vapi MCP server

Connect Vapi to AI assistants with Model Context Protocol (MCP)

Overview

The Vapi MCP server exposes Vapi APIs as tools via the Model Context Protocol (MCP), so you can manage assistants, phone numbers, and calls from any MCP-compatible AI assistant (like Claude) or agent framework.

Use this server to connect your AI workflows to real-world telephony, automate voice tasks, and build richer conversational agents.

Looking to use MCP tools inside a Vapi assistant? See the MCP Tool documentation for integrating external MCP servers with your Vapi agents.

Connect your coding agent directly to the hosted MCP server using its native MCP settings. The Vapi CLI is not required. For public agent skills and installation instructions, see VapiAI/skills.

If an earlier CLI release configured @vapi-ai/mcp-docs-server in your agent, replace that legacy entry with the hosted connection below, or with the documentation server if you only need docs search. Existing agent configurations are not removed automatically.

Server URL and sign-in

The hosted server uses Streamable HTTP at:

https://mcp.vapi.ai/mcp

You sign in with your Vapi account over OAuth. There is no API key to copy:

1

Add the server

Add https://mcp.vapi.ai/mcp to your MCP client using the instructions for your client below.

2

Sign in

Your client opens a browser window. Sign in to Vapi the same way you sign in to the dashboard: Google, GitHub, SSO, or email and password with MFA. If you’re already signed in to the dashboard, this step is skipped.

3

Choose an organization

Pick the Vapi organization this connection can access and approve. Tools then act as you, in that organization, with your role’s permissions.

Your client stores the session and refreshes it automatically, so you only sign in again if the session is revoked or you disconnect.

The hosted server no longer accepts Vapi API keys. If your client configuration sends an Authorization: Bearer header with an API key, remove the header and sign in with OAuth instead.

Connect your agent

Add the server to your user configuration:

claude mcp add --transport http --scope user vapi https://mcp.vapi.ai/mcp

Start a Claude Code session, run /mcp, select vapi, and choose Authenticate. Sign in and pick an organization in the browser.

See Claude Code MCP setup.

Once connected, try asking your agent: “List my Vapi assistants.”


Search the docs without signing in

For documentation search alone, connect your agent to Vapi’s documentation MCP server at https://docs.vapi.ai/_mcp/server. It needs no account and provides a searchDocs tool. The Vapi MCP server’s ask_vapi_docs tool runs the same search.

If your client can’t connect to a remote server directly, run it through the mcp-remote adapter:

{
"mcpServers": {
"vapi-docs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://docs.vapi.ai/_mcp/server"]
}
}
}

Available tools

The Vapi MCP server exposes the tools below.

Connection

ToolDescription
get_connection_infoShow the Vapi user, organization, and OAuth client this connection is authorized as

Documentation and reference

ToolDescription
ask_vapi_docsSearch Vapi documentation and return relevant passages with source URLs
get_api_schemaLook up a schema in the Vapi API reference, the OpenAPI spec the SDKs are generated from
search_skillsFind Vapi agent skills in the public VapiAI/skills repository
load_skillRead a public Vapi skill or one of its supporting files

The load_skill tool returns instructions for the agent to follow. It does not install skills or run scripts.

Assistants

ToolDescription
list_assistantsList all Vapi assistants
get_assistantGet a Vapi assistant by ID
create_assistantCreate a new Vapi assistant
update_assistantUpdate an existing Vapi assistant

Calls

ToolDescription
list_callsList all calls
get_callGet details for a specific call
create_callCreate an outbound call, now or scheduled

To schedule a call, pass the optional scheduledAt parameter to create_call.

The create_call tool places a real phone call.

Phone numbers

ToolDescription
list_phone_numbersList all Vapi phone numbers
get_phone_numberGet details of a specific phone number

Vapi tools

ToolDescription
list_toolsList all Vapi tools
get_toolGet details of a specific tool
create_toolCreate a new Vapi tool
update_toolUpdate an existing Vapi tool

Simulations

These tools drive simulations, which test an assistant against an AI tester.

ToolDescription
list_simulation_personalitiesList simulation personalities, which set how the AI tester behaves
create_simulation_personalityCreate a personality that sets how the AI tester behaves
list_simulation_scenariosList simulation scenarios, the AI tester’s intent and the checks that decide pass or fail
create_simulation_scenarioCreate a scenario: AI tester instructions plus the evaluations that decide pass or fail
list_simulationsList simulations, each pairing one scenario with one personality
create_simulationCreate a simulation that pairs a scenario with a personality
list_simulation_suitesList simulation suites, which are named groups of simulations
create_simulation_suiteCreate a suite that groups simulations so they can be run together
run_simulationsStart a run of simulations or suites against an assistant or squad
list_simulation_runsList simulation runs, newest first
get_simulation_runGet a run with its status, item counts, and item summaries
get_simulation_run_itemGet one run item in full, including results, call snapshots, and transcript

Each run_simulations tool call starts a billed simulation run. For more information, see Simulations overview.

Which tools succeed depends on your role in the organization you signed in to. A call that your role doesn’t permit fails with an authorization error.


Custom MCP clients

If you’re building your own MCP client, use an MCP SDK that implements MCP authorization. The server follows the standard flow:

  • An unauthenticated request gets 401 with a WWW-Authenticate header that points to the protected resource metadata at https://mcp.vapi.ai/.well-known/oauth-protected-resource/mcp.
  • That metadata names the authorization server. Clients register with Dynamic Client Registration or a Client ID Metadata Document, then use the authorization code flow with PKCE.
  • Request the scopes openid offline_access and the resource https://mcp.vapi.ai/mcp, then send the access token as Authorization: Bearer <token>.

FAQ

No. The hosted server only accepts OAuth sign-in. Remove any Authorization header or API key from your MCP configuration and follow the setup for your client above. API keys still work everywhere else in Vapi, including the API and server SDKs.

Each connection is bound to the organization you picked when you signed in. Ask your agent to run the get_connection_info tool to see which user and organization it is using. To switch, disconnect or clear the authentication in your client and sign in again. To use several organizations at once, add the server once per organization under different names, such as vapi-prod and vapi-staging.

The same things you can in the chosen organization, with your role’s permissions. If you lose access to the organization, the connection stops working on the next request. The connection can’t create or read API keys, credentials, or billing details.

Remove the server from your client, or use its clear-authentication option (for example /mcp in Claude Code, or Disconnect for Claude connectors).

OAuth sign-in needs a person to approve it in a browser. For unattended jobs, call the Vapi API directly with an API key, or use a server SDK.

The legacy HTTP+SSE endpoint (https://mcp.vapi.ai/sse) has been removed. Use Streamable HTTP at https://mcp.vapi.ai/mcp.

Clear the saved authentication for vapi in your client and connect again. Make sure you can sign in to the dashboard with the same account, and that you’re a member of the organization you pick. If your company manages MCP connections centrally, ask your admin to allow https://mcp.vapi.ai/mcp.

References