# How to connect V0 to Hermes Agent (paste one key, 44 tools) > Connect V0 to Hermes with ClawLink: paste your V0 key once and 44 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/v0 Most guides for giving Hermes Agent V0 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 V0 setup: pair once in the browser and your always-on Hermes agent can act on V0 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 V0. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect V0** — 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 v0 # connect V0 (browser OAuth) npx -y @useclawlink/cli actions v0 # list available actions npx -y @useclawlink/cli run v0 --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 V0 in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your V0 API key once. Verify the connection by asking Hermes: > Use V0 to download chat version 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 V0 is connected in the dashboard, that agent calls the same 44 V0 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). ## V0 MCP for Hermes Looking for a V0 MCP server for Hermes Agent? ClawLink connects V0 to Hermes Agent and exposes 44 V0 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 V0 integration](https://claw-link.dev/openclaw/v0) works the same way. ## What the Hermes Agent V0 integration can do 44 V0 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 44. ### 30 of 44 V0 tools for Hermes | Tool | What it does | |---|---| | **Download chat version** `v0_download_chat_version` | Download all files for a specific chat version as a zip or tarball archive | | **Export project code** `v0_export_project_code` | Export a deployable snapshot of a v0 chat version by retrieving all files (including | | **Find chats** `v0_find_chats` | Retrieve a list of chats | | **Find projects** `v0_find_projects` | Retrieve a list of projects associated with the authenticated user | | **Find vercel projects** `v0_find_vercel_projects` | Retrieve a list of Vercel projects linked to the user's v0 workspace | | **Get chat** `v0_get_chat` | Retrieve the full details of a specific chat using its chatId | | **Get chat project** `v0_get_chat_project` | Retrieve the v0 project associated with a given chat | | **Get deployment errors** `v0_get_deployment_errors` | Retrieve errors for a specific deployment | | **Get deployment logs** `v0_get_deployment_logs` | Retrieve logs for a specific deployment | | **Get hook** `v0_get_hook` | Retrieve detailed information about a specific webhook by its ID | | **Get message** `v0_get_message` | Retrieve detailed information about a specific message within a chat | | **Get project** `v0_get_project` | Retrieve the details of a specific v0 project by its ID, including associated chats and metadata | | **Get project env var** `v0_get_project_env_var` | Retrieve a specific environment variable for a given project by its ID, including its value | | **Get rate limits** `v0_get_rate_limits` | Retrieve the current rate limits for the authenticated user | | **Get usage report v0** `v0_get_usage_report_v0` | Retrieve detailed usage events including costs, models used, and metadata | | **Get user** `v0_get_user` | Retrieve the currently authenticated user's information | | **Get user billing** `v0_get_user_billing` | Fetch billing usage and quota information for the authenticated user | | **Get user plan v0** `v0_get_user_plan_v0` | Retrieve the authenticated user's subscription plan details including billing cycle and balance | | **Get user scopes** `v0_get_user_scopes` | Retrieve all accessible scopes for the authenticated user, such as personal workspaces or | | **List chat versions** `v0_list_chat_versions` | Retrieve all versions (iterations) for a specific chat, ordered by creation date (newest first) | | **List deployments** `v0_list_deployments` | Retrieve a list of deployments for a given project, chat, and version | | **List hooks** `v0_list_hooks` | Retrieve all webhooks tied to chat events or deployments | | **List messages** `v0_list_messages` | Retrieve all messages within a specific chat | | **List project env vars** `v0_list_project_env_vars` | Retrieve all environment variables for a project with optional decryption | | **Assign chat to project** `v0_assign_chat_to_project` | Assign a chat to a project | | **Chat completions** `v0_chat_completions` | Generate a chat model response given a list of messages | | **Create hook v0** `v0_create_hook_v0` | Create a new webhook subscription for receiving event notifications | | **Create project** `v0_create_project` | Create a new v0 project container for chats and code generation | | **Create project env vars** `v0_create_project_env_vars` | Create new environment variables for a v0 project | | **Create vercel project** `v0_create_vercel_project` | Link a Vercel project to an existing v0 project | ## Example prompts **Download Chat Version** > Use V0 to download chat version and walk me through the result in plain English. **Export Project Code** > Use V0 to export project code and walk me through the result in plain English. **Find Chats** > Use V0 to find chats and walk me through the result in plain English. **Find Projects** > Use V0 to find projects 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 V0 working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the V0 API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected V0 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 V0. | 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 V0 actions to the runtime in a format your agent can reliably use. | 44 tools for V0 are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes V0 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 V0 in the browser, and the 44 tools above work from chat. There is no SDK and no config file, and the V0 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 V0 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 V0 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 V0 tools V0 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 V0 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. ### V0 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 V0 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 V0 integration? Yes. ClawLink is the fastest way to connect Hermes to V0: link your V0 account once in the browser and Hermes Agent can call the V0 API through 44 ready-made tools — no custom code or token handling. ### How do I connect V0 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 V0 in the dashboard and Hermes can use it from the next message — no config files, and the V0 key you paste is stored server-side instead of in your environment. ### How long does it take to connect V0 to Hermes Agent? About two minutes. Sign in, click Connect next to V0 in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring V0 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 V0 working from chat. ### Hermes paired but still can't use V0 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 - [Hermes DataRobot integration](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. - [Chatbotkit tools](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. - [Hermes Just One API integration](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.