# How to connect Vapi to Hermes Agent (paste one key, 38 tools) > Connect Vapi to Hermes with ClawLink: paste your Vapi key once and 38 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/vapi Most guides for giving Hermes Agent Vapi access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Vapi setup: pair once in the browser and your always-on Hermes agent can act on Vapi for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect Hermes to Vapi. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Vapi** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect vapi # connect Vapi (browser OAuth) npx -y @useclawlink/cli actions vapi # list available actions npx -y @useclawlink/cli run vapi --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash hermes plugins install ClawLink-HQ/hermes-plugin --enable hermes clawlink begin # prints an approval link — open it and approve hermes clawlink finish # after approving in the browser hermes clawlink test ``` Then connect Vapi in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Vapi API key once. Verify the connection by asking Hermes: > Use Vapi to call controller find all and walk me through the result in plain English. ### Using a different agent? The Hermes 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: ```bash npx -y @useclawlink/cli login ``` `login` 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](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Vapi MCP for Hermes Looking for a Vapi MCP server for Hermes Agent? ClawLink connects Vapi to Hermes Agent and exposes 38 Vapi tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Vapi integration](https://claw-link.dev/openclaw/vapi) works the same way. ## What the Hermes Agent Vapi integration can do 38 Vapi tools are ready for Hermes Agent 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 Hermes | 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 | ## Example prompts **Call Controller Find All** > Use Vapi to call controller find all and walk me through the result in plain English. **Chat Controller Get Chat** > Use Vapi to chat controller get chat and walk me through the result in plain English. **Create Analytics Query** > Create it in Vapi for me, then confirm the important fields before you finish. **Eval Controller Get** > 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 Hermes Agent. 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 Hermes Agent 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](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Vapi Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ### 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. ### Is there a Hermes Agent Vapi integration? Yes. ClawLink is the fastest way to connect Hermes to Vapi: link your Vapi account once in the browser and Hermes Agent can call the Vapi API through 38 ready-made tools — no custom code or token handling. ### How do I connect Vapi to Hermes with ClawLink? Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Vapi in the dashboard and Hermes can use it 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 Hermes Agent? About two minutes. Sign in, click Connect next to Vapi in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Vapi working from chat. ### Hermes paired but still can't use Vapi Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`. ## Related - [Connect DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets. - [Hermes Chatbotkit integration](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications. - [Just One API](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.