How to connect Vapi to OpenClaw
Connect Vapi to OpenClaw with ClawLink: paste your Vapi key once and 38 tools work from chat. No MCP server to run, nothing stored on your machine.
VapiAPI KEYMCPVapi is a voice AI platform that enables developers to build, test, and deploy voice agents with natural conversations, real-time responses, and seamless integration capabilities.. Once connected, OpenClaw can read and act on Vapi from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Vapi access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Vapi setup: install one ClawHub skill, connect Vapi in the browser, and OpenClaw can call real Vapi actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Vapi.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Vapi
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Vapi?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Vapi in the ClawLink dashboard — paste your Vapi API key once.
Verify the connection by asking OpenClaw:
Use Vapi to call controller find all and walk me through the result in plain English.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Vapi is connected in the dashboard, that agent calls the same 38 Vapi tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Vapi MCP for OpenClaw
Looking for a Vapi MCP server for OpenClaw? ClawLink connects Vapi to OpenClaw and exposes 38 Vapi tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Vapi integration works the same way.
What the OpenClaw Vapi integration can do
38 Vapi tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 38.
30 of 38 Vapi tools for OpenClaw
| Tool | What it does |
|---|---|
Call controller find all vapi_call_controller_find_all | List calls from Vapi |
Chat controller get chat vapi_chat_controller_get_chat | Fetch chat details by ID |
Create analytics query vapi_create_analytics_query | Create and execute analytics queries on VAPI data |
Eval controller get vapi_eval_controller_get | Retrieve an eval by its ID |
Get assistant vapi_get_assistant | Retrieve a specific assistant by ID from Vapi |
Get call vapi_get_call | Fetch call details by ID |
Get file vapi_get_file | Retrieve a file by its ID from Vapi |
Get monitoring vapi_get_monitoring | Retrieve monitoring policies from Vapi |
Get structured outputs vapi_get_structured_outputs | List structured outputs with optional filtering |
Insight controller find all vapi_insight_controller_find_all | Retrieve insights from VAPI |
List assistants vapi_list_assistants | List all assistants in your VAPI organization |
List chats vapi_list_chats | Retrieve a list of chat conversations from VAPI |
List evals vapi_list_evals | Retrieve a paginated list of evals from Vapi |
List phone numbers vapi_list_phone_numbers | List phone numbers in the Vapi organization |
List provider resources vapi_list_provider_resources | Retrieve provider resources from Vapi (e.g., 11labs pronunciation dictionaries) |
Scorecard controller get paginated vapi_scorecard_controller_get_paginated | Retrieve a paginated list of scorecards from Vapi |
Session controller find all paginated vapi_session_controller_find_all_paginated | Retrieve a paginated list of sessions from VAPI |
Tool controller find one vapi_tool_controller_find_one | Fetch tool details by ID |
Tool controller test code execution vapi_tool_controller_test_code_execution | Test TypeScript code execution in Vapi's code tool environment |
Assistant controller update vapi_assistant_controller_update | Update an existing Vapi assistant configuration |
Create assistant vapi_create_assistant | Create a new Vapi assistant with specified transcriber, voice, and AI model configurations |
Create eval vapi_create_eval | Create an eval for testing conversation flows |
Create open AI chat vapi_create_open_ai_chat | Create an OpenAI-compatible chat using the Vapi API |
Create policy vapi_create_policy | Create a monitoring policy in VAPI |
Create provider resource vapi_create_provider_resource | Create an 11Labs pronunciation dictionary resource |
Create scorecard vapi_create_scorecard | Create a scorecard for observability and evaluation |
Eval controller update vapi_eval_controller_update | Update an existing eval in Vapi |
Patch insight insight vapi_patch_insight_insight | Update an existing insight configuration in VAPI |
Phone number controller create vapi_phone_number_controller_create | Create a phone number with VAPI |
Session controller create vapi_session_controller_create | Create a new session in Vapi |
Try it: find the Vapi tool you need
Browse the 30 Vapi tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Vapi to call controller find all and walk me through the result in plain English.
Use Vapi to chat controller get chat and walk me through the result in plain English.
Create it in Vapi for me, then confirm the important fields before you finish.
Use Vapi to eval controller get and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Vapi working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Vapi API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Vapi account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Vapi. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Vapi actions to the runtime in a format your agent can reliably use. | 38 tools for Vapi are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Vapi to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Vapi in the browser, and the 38 tools above work from chat. There is no SDK and no config file, and the Vapi key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Vapi skill but can't call the tools
The ClawHub skill teaches OpenClaw about Vapi, but the calls run through the ClawLink plugin and your connected account. Make sure Vapi is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Vapi from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Vapi tools
Vapi tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Vapi call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Vapi returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Vapi has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Vapi integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Vapi: link your Vapi account once in the browser and OpenClaw can call the Vapi API through 38 ready-made tools — no custom code or token handling.
How do I add Vapi to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Vapi skill from ClawHub, then you click Connect in the dashboard to authorize Vapi. OpenClaw calls the tools from the next message — no config files, and the Vapi key you paste is stored server-side instead of in your environment.
How long does it take to connect Vapi to OpenClaw?
About two minutes. Sign in, click Connect next to Vapi in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Vapi up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Vapi working from chat.
OpenClaw installed the Vapi skill but can't call the tools
The ClawHub skill teaches OpenClaw about Vapi, but the calls run through the ClawLink plugin and your connected account. Make sure Vapi is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Related
OpenClaw DataRobot integration
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw Chatbotkit integration
ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
OpenClaw Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.