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:
You sign in with your Vapi account over OAuth. There is no API key to copy:
Add the server
Add https://mcp.vapi.ai/mcp to your MCP client using the instructions for your client below.
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.
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
Claude Code
Claude
Codex
Cursor
VS Code
Hermes
Other clients
Add the server to your user configuration:
Start a Claude Code session, run /mcp, select vapi, and choose Authenticate. Sign in and pick an organization in the browser.
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:
Available tools
The Vapi MCP server exposes the tools below.
Connection
Documentation and reference
The load_skill tool returns instructions for the agent to follow. It does not install skills or run scripts.
Assistants
Calls
To schedule a call, pass the optional scheduledAt parameter to create_call.
The create_call tool places a real phone call.
Phone numbers
Vapi tools
Simulations
These tools drive simulations, which test an assistant against an AI tester.
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
401with aWWW-Authenticateheader that points to the protected resource metadata athttps://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_accessand the resourcehttps://mcp.vapi.ai/mcp, then send the access token asAuthorization: Bearer <token>.
FAQ
Can I still use a Vapi API key with the hosted MCP server?
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.
How do I use a different organization?
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.
What can the connection access?
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.
How do I disconnect?
Remove the server from your client, or use its clear-authentication option (for example /mcp in Claude Code, or Disconnect for Claude connectors).
Can I use the MCP server in CI or other headless automation?
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.
What happened to the SSE endpoint?
The legacy HTTP+SSE endpoint (https://mcp.vapi.ai/sse) has been removed. Use Streamable HTTP at https://mcp.vapi.ai/mcp.
Sign-in fails or keeps asking me to authenticate
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.