# How to connect Botster to OpenClaw (paste one key, 11 tools) > Connect Botster to OpenClaw 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/openclaw/botster The usual route to Botster 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 Botster setup: install one ClawHub skill, connect Botster in the browser, and OpenClaw can call real Botster 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 Botster. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Botster** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw 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 setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then 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 Botster in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Botster API key once. Verify the connection by asking OpenClaw: > Use Botster to calculate bot cost 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: ```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 OpenClaw Looking for a Botster MCP server for OpenClaw? ClawLink connects Botster to OpenClaw 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 Hermes instead? The [Hermes Botster integration](https://claw-link.dev/hermes/botster) works the same way. ## What the OpenClaw Botster integration can do 11 Botster tools are ready for OpenClaw 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 OpenClaw | 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 OpenClaw. 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 OpenClaw 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. ### OpenClaw installed the Botster skill but can't call the tools The ClawHub skill teaches OpenClaw about Botster, but the calls run through the ClawLink plugin and your connected account. Make sure Botster 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 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 OpenClaw Botster integration? Yes. ClawLink is the fastest way to connect OpenClaw to Botster: link your Botster account once in the browser and OpenClaw can call the Botster API through 11 ready-made tools — no custom code or token handling. ### How do I add Botster to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Botster skill from ClawHub, then you click Connect in the dashboard to authorize Botster. OpenClaw calls the tools 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 OpenClaw? About two minutes. Sign in, click Connect next to Botster in the dashboard, authenticate, and OpenClaw 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Botster working from chat. ### OpenClaw installed the Botster skill but can't call the tools The ClawHub skill teaches OpenClaw about Botster, but the calls run through the ClawLink plugin and your connected account. Make sure Botster 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 - [DataRobot](https://claw-link.dev/openclaw/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/openclaw/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/openclaw/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.