# How to connect Botstar to Hermes Agent (paste one key, 31 tools) > Connect Botstar to Hermes with ClawLink: paste your Botstar key once and 31 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/botstar Most guides for giving Hermes Agent Botstar 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 Botstar setup: pair once in the browser and your always-on Hermes agent can act on Botstar 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 Botstar. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Botstar** — 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 botstar # connect Botstar (browser OAuth) npx -y @useclawlink/cli actions botstar # list available actions npx -y @useclawlink/cli run botstar --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 Botstar in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Botstar API key once. Verify the connection by asking Hermes: > Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention. ### 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 Botstar is connected in the dashboard, that agent calls the same 31 Botstar 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). ## Botstar MCP for Hermes Looking for a Botstar MCP server for Hermes Agent? ClawLink connects Botstar to Hermes Agent and exposes 31 Botstar 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 Botstar integration](https://claw-link.dev/openclaw/botstar) works the same way. ## What the Hermes Agent Botstar integration can do 31 Botstar tools are ready for Hermes Agent once the account is connected. The 27 below are the ones people reach for most; your agent can call all 31. ### 27 of 31 Botstar tools for Hermes | Tool | What it does | |---|---| | **Get bot** `botstar_get_bot` | Get your bot by bot ID | | **Get bot app ID** `botstar_get_bot_app_id` | Retrieve the BotStar application ID (`appId`) | | **Get cms entity** `botstar_get_cms_entity` | Get a specific CMS entity by ID | | **Get entity item** `botstar_get_entity_item` | Retrieve a specific item from a CMS entity with all field values | | **List bot attributes** `botstar_list_bot_attributes` | Get all bot attributes from BotStar | | **List bots** `botstar_list_bots` | Get your list of bots | | **List cms entities** `botstar_list_cms_entities` | Retrieve all CMS entities for a bot | | **List entity items** `botstar_list_entity_items` | Retrieve all entity items with pagination support | | **Livechat boot** `botstar_livechat_boot` | Reinitialize the live chat widget with provided data | | **Livechat close** `botstar_livechat_close` | Hide the live chat window | | **Livechat on close** `botstar_livechat_on_close` | Register a callback when the chat window is closed | | **Livechat on open** `botstar_livechat_on_open` | Register a callback when the chat window is opened | | **Livechat open** `botstar_livechat_open` | Show the live chat window | | **Livechat update** `botstar_livechat_update` | Update user details on the current live chat session | | **Webview get parameter** `botstar_webview_get_parameter` | Retrieve a parameter value passed from the BotStar chatbot to the webview | | **Webview send response** `botstar_webview_send_response` | Send data from the webview back to the BotStar chatbot | | **Create bot** `botstar_create_bot` | Create a new bot in BotStar | | **Create bot attribute** `botstar_create_bot_attribute` | Create a new bot attribute in BotStar | | **Create cms entity** `botstar_create_cms_entity` | Create a CMS entity in BotStar with a name and optional fields | | **Create entity fields** `botstar_create_entity_fields` | Create entity field(s) in BotStar CMS | | **Create entity item** `botstar_create_entity_item` | Create a new entity item in BotStar CMS | | **Create user attributes** `botstar_create_user_attributes` | Create custom user attributes in BotStar | | **Publish bot** `botstar_publish_bot` | Publish a bot to live | | **Update bot attribute** `botstar_update_bot_attribute` | Update a bot attribute in BotStar | | **Update cms entity** `botstar_update_cms_entity` | Update a CMS entity in BotStar | | **Update entity fields** `botstar_update_entity_fields` | Update entity field(s) in BotStar CMS | | **Update entity item** `botstar_update_entity_item` | Update a CMS entity item in BotStar | ## Example prompts **Get Bot** > Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention. **Get Bot App Id** > Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention. **Get Cms Entity** > Pull the relevant data from Botstar, summarize it in plain English, and point out anything that needs attention. **Get Entity Item** > Pull the relevant data from Botstar, 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 Botstar working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Botstar API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Botstar 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 Botstar. | 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 Botstar actions to the runtime in a format your agent can reliably use. | 31 tools for Botstar are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Botstar 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 Botstar in the browser, and the 31 tools above work from chat. There is no SDK and no config file, and the Botstar 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 Botstar 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 Botstar 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 Botstar tools Botstar 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 Botstar 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. ### Botstar 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 Botstar 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 Botstar integration? Yes. ClawLink is the fastest way to connect Hermes to Botstar: link your Botstar account once in the browser and Hermes Agent can call the Botstar API through 31 ready-made tools — no custom code or token handling. ### How do I connect Botstar 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 Botstar in the dashboard and Hermes can use it from the next message — no config files, and the Botstar key you paste is stored server-side instead of in your environment. ### How long does it take to connect Botstar to Hermes Agent? About two minutes. Sign in, click Connect next to Botstar in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Botstar 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 Botstar working from chat. ### Hermes paired but still can't use Botstar 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. - [Connect Chatbotkit](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. - [Connect 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.