What it does
The Vapi MCP Server lets any agent or app that supports the Model Context Protocol build AI voice assistants and phone agents with Vapi. Its tools cover assistants, calls, phone numbers, custom function-calling tools, Vapi documentation lookup, public Vapi skills and simulations. Outbound calls can start immediately or be scheduled, and assistant prompts can use variables written in double curly braces, including built-in values such as the current UTC date and the customer's phone number.
A developer would reach for it when an MCP-capable client should create, update or inspect Vapi assistants, review call history, manage phone numbers or define API-integration tools. The documentation tool returns passages from the Vapi docs for the calling agent to use, and the skills tools read instructions from the public VapiAI/skills repository.
The hosted server needs no installation: the client connects over Streamable HTTP with a Vapi API key in a bearer header. A local stdio option exists for clients that only support local servers, configured with the same key as VAPI_TOKEN. List tools return pages of up to 10 items.
Limitations and requirements
A Vapi API key is required. The server requires VAPI_TOKEN at startup, including for the documentation and skills tools. The legacy SSE endpoint is deprecated. Documentation and skills tools need outbound HTTPS access, and GitHub's unauthenticated API rate limits apply to skills discovery. Do not include secrets or private customer data in documentation questions. load_skill returns one text file at a time, up to 512 KB.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Cline MCP Marketplace first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source
58
As shown on cline.bot when we last read it