Vapi MCP server

Endpoint: https://mcp.vapi.ai/mcp · Authentication: Bearer token

Lists, creates, and updates Vapi voice assistants, phone numbers, and tools and places outbound calls. Requires a Vapi API key as a bearer token.

Test it live Run the release-readiness report

How do I authenticate?

Create a scoped provider token and supply it using the credential header and value format documented in the client setup below. Keep credentials out of shared URLs and logs.

Authentication and connection guide

Connection specification

Remote endpoint: https://mcp.vapi.ai/mcp
Browser access: Not yet measured
Declared MCP transport: Streamable HTTP
Live-validated MCP transport: Not yet verified — Latest validation did not verify a transport
Declared authentication: Bearer token
Detected authentication: Bearer token detected or retained from publisher evidence
Protocol lifecycle: Not yet negotiated
Required header: Authorization — Vapi private API key: Bearer <VAPI_API_KEY>
Category: Communication

Product documentation · Source repository · Official listing documentation

More Communication MCP servers · Browse all MCP servers · Test this endpoint in the MCP Playground

Authorization setup

bearer token required

Use the publisher-documented bearer token route. Keep the credential in protected client storage and replace only the named placeholder at connection time.

Safe header template: Bearer <VAPI_API_KEY>. Replace only the named placeholder in protected client configuration.

Publisher documentation

Connect it

Live-validated endpoint: https://mcp.vapi.ai/mcp · Streamable HTTP. Bearer token authentication uses a named environment placeholder.

Agent prompt for Claude Code or Codex

Add the Vapi MCP server to my MCP client configuration and verify that it works.

What it is: Lists, creates, and updates Vapi voice assistants, phone numbers, and tools and places outbound calls. Requires a Vapi API key as a bearer token.
Server URL: https://mcp.vapi.ai/mcp
Transport: Streamable HTTP (remote MCP server, no local install).
Authentication: Bearer token. Bearer token authentication uses a named environment placeholder.
Tools: not yet observed by mcptest; tools/list will show them.
Reference: https://mcptest.io/servers/vapi/

Steps:
1. Work out which MCP client I use (Claude Code, Codex, Cursor, VS Code or another) and add the server under the name "vapi" in that client's MCP configuration, user scope unless I ask otherwise.
   Claude Code: claude mcp add --transport http --scope user --header 'Authorization: Bearer '"${VAPI_API_KEY}" 'vapi' 'https://mcp.vapi.ai/mcp'
   Codex: codex mcp add 'vapi' --url 'https://mcp.vapi.ai/mcp' --bearer-token-env-var 'VAPI_API_KEY'
   Other clients: use the setup for that client on the reference page.
2. Never write a credential value into a file that could be committed; reference an environment variable or the client's secret store, and ask me for any value you need.
3. Verify: connect to the server and call tools/list. Confirm the tools above are listed, and report any sign-in step I still have to complete.

Claude Code setup

Run in a terminal. This user-scoped entry is available across projects.

claude mcp add --transport http --scope user --header 'Authorization: Bearer '"${VAPI_API_KEY}" 'vapi' 'https://mcp.vapi.ai/mcp'

Store VAPI_API_KEY in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <VAPI_API_KEY>.

Codex CLI setup

Run in a terminal; Codex stores the entry in ~/.codex/config.toml.

codex mcp add 'vapi' --url 'https://mcp.vapi.ai/mcp' --bearer-token-env-var 'VAPI_API_KEY'

Store VAPI_API_KEY in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <VAPI_API_KEY>.

Cursor setup

Add to .cursor/mcp.json for this project, or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "vapi": {
      "url": "https://mcp.vapi.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:VAPI_API_KEY}"
      }
    }
  }
}

Store VAPI_API_KEY in your operating system keychain, secret manager, or protected environment; never commit the value. The Authorization header syntax is Bearer <VAPI_API_KEY>.

VS Code setup

Add to .vscode/mcp.json, or run “MCP: Open User Configuration” for a private user-level entry.

{
  "servers": {
    "vapi": {
      "type": "http",
      "url": "https://mcp.vapi.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${input:vapi_api_key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "vapi_api_key",
      "description": "VAPI_API_KEY for Vapi",
      "password": true
    }
  ]
}

VS Code requests VAPI_API_KEY as a masked input; use a secret manager and do not put a default value in mcp.json. The Authorization syntax remains Bearer <VAPI_API_KEY>.

Claude setup

Add the endpoint above in Claude:

Customize > Connectors > Add custom connector
Team/Enterprise: Organization settings > Connectors > Add > Custom > Web

Claude Desktop setup

Add the endpoint above in Claude Desktop:

Remote: Customize > Connectors (same as claude.ai)
Local: Settings > Developer > Edit Config, or Settings > Extensions for .mcpb files
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), local servers only

ChatGPT setup

Add the endpoint above in ChatGPT:

ChatGPT web: Plugins > Add custom MCP server, then configure authentication and accept the risk warning

Windsurf setup

Add the endpoint above in Windsurf:

~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows), serverUrl or url
Cascade panel > ... > MCPs > Open MCP config file

Gemini CLI setup

Add the endpoint above in Gemini CLI:

gemini mcp add --transport http <name> <url>
~/.gemini/settings.json (user) or .gemini/settings.json (project), mcpServers

MCP SDK setup

Add the endpoint above in MCP SDK:

Programmatic: new Client(...).connect(new StreamableHTTPClientTransport(url))

Client compatibility

Client	Status	Why
Claude Code	Supported	Claude Code supports Streamable HTTP servers and bearer-token headers.
Codex	Supported	Codex supports Streamable HTTP servers and bearer-token headers.
Cursor	Supported	Cursor supports Streamable HTTP servers and bearer-token headers.
VS Code	Supported	VS Code supports Streamable HTTP servers and bearer-token headers.
Claude	Partial	Claude supports bearer-token headers only in limited availability. Request-header authentication is in beta and available to a limited set of organizations.
Claude Desktop	Partial	Claude Desktop supports bearer-token headers only in limited availability. Request-header authentication is in beta and available to a limited set of organizations.
ChatGPT	Not supported	ChatGPT does not support bearer-token headers. Only the OAuth-issued token is sent; ChatGPT cannot present custom API keys.
Windsurf	Supported	Windsurf supports Streamable HTTP servers and bearer-token headers.
Gemini CLI	Supported	Gemini CLI supports Streamable HTTP servers and bearer-token headers.
MCP SDK	Supported	MCP SDK supports Streamable HTTP servers and bearer-token headers.

Computed from this server's validated transport, protocol and authentication against documented client support. Checks the catalog has not observed are not counted.

Similar servers

Slack — Remote MCP server for Slack messages, channels, users, canvases, and collaboration context. OAuth 2.1
Intercom — Intercom's hosted MCP server provides customer-support context through conversations, contacts, search, and retrieval tools. OAuth 2.1
Resend — Sends and schedules email and manages Resend domains, audiences, contacts, broadcasts, and API keys. Requires Resend sign-in through OAuth. OAuth 2.1
Courier — Sends notifications and manages Courier users, lists, templates, journeys, preferences, tenants, and brands through the Courier API. Requires a Courier API key in the api_key header. API key
AgentMail — Creates and manages AgentMail inboxes, threads, messages, drafts, and attachments for AI agents. Requires AgentMail sign-in through OAuth; an x-api-key header is also documented. OAuth 2.1
Infobip SMS — Sends, previews, and schedules SMS messages through Infobip and reads delivery reports and message logs. Requires Infobip sign-in through OAuth; an App API key header is also documented. OAuth 2.1

Guides for this server

Watch this server for breaking changes

Share and embed

Maintain Vapi? Embed this badge in your README. It follows the latest catalog validation result and links to this server profile.

Markdown

[![Tested on mcptest.io](https://mcptest.io/badge/server/vapi.svg)](https://mcptest.io/servers/vapi/)

HTML

<a href="https://mcptest.io/servers/vapi/"><img src="https://mcptest.io/badge/server/vapi.svg" alt="Tested on mcptest.io"></a>

reStructuredText

.. image:: https://mcptest.io/badge/server/vapi.svg
   :alt: Tested on mcptest.io
   :target: https://mcptest.io/servers/vapi/

Latest validation evidence

Validation status: Online when last tested
Validation checked at: Oct 26, 2026 at 11:07 AM
Validation detail: Authentication challenge at https://mcp.vapi.ai/mcp returned HTTP 401; endpoint was reachable but did not complete an MCP probe; authentication bearer-token

Tool inventory

Requires authorization; inventory not observed

The catalog validator lists tools only on servers that answer without credentials. Vapi asks for a bearer token first, so its tools, resources and prompts were not observed. Connect in the Playground with your own credentials to list them.