# How to connect Botster to Hermes Agent (paste one key, 11 tools) > Connect Botster to Hermes with ClawLink: paste your Botster key once and 11 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/botster Most guides for giving Hermes Agent Botster 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 Botster setup: pair once in the browser and your always-on Hermes agent can act on Botster 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 Botster. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Botster** — 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 botster # connect Botster (browser OAuth) npx -y @useclawlink/cli actions botster # list available actions npx -y @useclawlink/cli run botster --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 Botster in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Botster API key once. Verify the connection by asking Hermes: > Use Botster to calculate bot cost 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 Botster is connected in the dashboard, that agent calls the same 11 Botster 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). ## Botster MCP for Hermes Looking for a Botster MCP server for Hermes Agent? ClawLink connects Botster to Hermes Agent and exposes 11 Botster 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 Botster integration](https://claw-link.dev/openclaw/botster) works the same way. ## What the Hermes Agent Botster integration can do 11 Botster tools are ready for Hermes Agent once the account is connected. The 9 below are the ones people reach for most; your agent can call all 11. ### 9 of 11 Botster tools for Hermes | Tool | What it does | |---|---| | **Calculate bot cost** `botster_calculate_bot_cost` | Calculate the credit price of one intended bot launch using the same input and bot-specific | | **Get credits** `botster_get_credits` | Return the connected Botster account's available credit balance; use this before launching or | | **Get job** `botster_get_job` | Get one job's status and data-run identifiers required to retrieve run results | | **Get run results** `botster_get_run_results` | Return the complete bot-specific JSON for one data run identified from GET_JOB in the results | | **List bots** `botster_list_bots` | List or search bots available to the connected account and return their identifiers for cost | | **List jobs** `botster_list_jobs` | List jobs belonging to the connected Botster account and return job identifiers for inspection | | **Set job archived** `botster_set_job_archived` | Archive a Botster job or restore it from the archive by setting its desired archived state | | **Launch bot** `botster_launch_bot` | Launch a Botster bot, creating external work that may spend account credits | | **Restart job** `botster_restart_job` | Restart an existing Botster job, creating renewed external work that may repeat the bot's | ## Example prompts **Calculate Bot Cost** > Use Botster to calculate bot cost and walk me through the result in plain English. **Get Credits** > Pull the relevant data from Botster, summarize it in plain English, and point out anything that needs attention. **Get Job** > Pull the relevant data from Botster, summarize it in plain English, and point out anything that needs attention. **Get Run Results** > Pull the relevant data from Botster, summarize it in plain English, and point out anything that needs attention. ## 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 Botster working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Botster API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Botster 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 Botster. | 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 Botster actions to the runtime in a format your agent can reliably use. | 11 tools for Botster are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Botster 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 Botster in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Botster 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 Botster 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 Botster 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 Botster tools Botster 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 Botster 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. ### Botster 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 Botster 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 Botster integration? Yes. ClawLink is the fastest way to connect Hermes to Botster: link your Botster account once in the browser and Hermes Agent can call the Botster API through 11 ready-made tools — no custom code or token handling. ### How do I connect Botster 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 Botster in the dashboard and Hermes can use it from the next message — no config files, and the Botster key you paste is stored server-side instead of in your environment. ### How long does it take to connect Botster to Hermes Agent? About two minutes. Sign in, click Connect next to Botster in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Botster 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 Botster working from chat. ### Hermes paired but still can't use Botster 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 - [DataRobot tools](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.