# How to connect Browseai to OpenClaw (paste one key, 11 tools) > Connect Browseai to OpenClaw with ClawLink: paste your Browseai 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/browseai The usual route to Browseai 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 Browseai setup: install one ClawHub skill, connect Browseai in the browser, and OpenClaw can call real Browseai 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 Browseai. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Browseai** — 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 browseai # connect Browseai (browser OAuth) npx -y @useclawlink/cli actions browseai # list available actions npx -y @useclawlink/cli run browseai --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 Browseai in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Browseai API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Browseai, summarize it in plain English, and point out anything that needs attention. ### 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 Browseai is connected in the dashboard, that agent calls the same 11 Browseai 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). ## Browseai MCP for OpenClaw Looking for a Browseai MCP server for OpenClaw? ClawLink connects Browseai to OpenClaw and exposes 11 Browseai 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 Browseai integration](https://claw-link.dev/hermes/browseai) works the same way. ## What the OpenClaw Browseai integration can do 11 Browseai 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 Browseai tools for OpenClaw | Tool | What it does | |---|---| | **Get robot tasks** `browseai_get_robot_tasks` | Retrieves a paginated list of all tasks (execution runs) for a specific Browse AI robot | | **Get robots** `browseai_get_robots` | Retrieves a list of all robots (automated web tasks) under your Browse AI account | | **Get system status** `browseai_get_system_status` | Check the operational status of Browse AI infrastructure, including the tasks queue condition | | **Get task details** `browseai_get_task_details` | Retrieves detailed information about a specific Browse AI task by robot ID and task ID | | **List robot webhooks** `browseai_list_robot_webhooks` | Retrieve all webhooks configured for a specific Browse AI robot | | **Bulk run tasks** `browseai_bulk_run_tasks` | Allows users to bulk run up to 1,000 tasks per API call using a specified robot | | **Create monitor** `browseai_create_monitor` | Creates a new monitor for a Browse AI robot to automatically track website changes over time | | **Create webhook** `browseai_create_webhook` | Creates a new webhook for a Browse AI robot | | **Run robot** `browseai_run_robot` | Triggers the execution of a Browse.ai robot to extract data from websites | ## Example prompts **Get Robot Tasks** > Pull the relevant data from Browseai, summarize it in plain English, and point out anything that needs attention. **Get Robots** > Pull the relevant data from Browseai, summarize it in plain English, and point out anything that needs attention. **Get System Status** > Pull the relevant data from Browseai, summarize it in plain English, and point out anything that needs attention. **Get Task Details** > Pull the relevant data from Browseai, 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 Browseai working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Browseai API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Browseai 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 Browseai. | 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 Browseai actions to the runtime in a format your agent can reliably use. | 11 tools for Browseai are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Browseai 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 Browseai in the browser, and the 11 tools above work from chat. There is no SDK and no config file, and the Browseai 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 Browseai skill but can't call the tools The ClawHub skill teaches OpenClaw about Browseai, but the calls run through the ClawLink plugin and your connected account. Make sure Browseai 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 Browseai 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 Browseai tools Browseai 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 Browseai 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. ### Browseai 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 Browseai has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Browseai integration? Yes. ClawLink is the fastest way to connect OpenClaw to Browseai: link your Browseai account once in the browser and OpenClaw can call the Browseai API through 11 ready-made tools — no custom code or token handling. ### How do I add Browseai to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Browseai skill from ClawHub, then you click Connect in the dashboard to authorize Browseai. OpenClaw calls the tools from the next message — no config files, and the Browseai key you paste is stored server-side instead of in your environment. ### How long does it take to connect Browseai to OpenClaw? About two minutes. Sign in, click Connect next to Browseai in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Browseai 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 Browseai working from chat. ### OpenClaw installed the Browseai skill but can't call the tools The ClawHub skill teaches OpenClaw about Browseai, but the calls run through the ClawLink plugin and your connected account. Make sure Browseai 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. - [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. - [Connect 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.