How to connect Browserbase to OpenClaw
Connect Browserbase to OpenClaw with ClawLink: paste your Browserbase key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine.

Browserbase is a serverless platform that enables developers to run, manage, and monitor headless browsers at scale, offering seamless integration with tools like Playwright, Puppeteer, and Selenium.. Once connected, OpenClaw can read and act on Browserbase from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Browserbase 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 Browserbase setup: install one ClawHub skill, connect Browserbase in the browser, and OpenClaw can call real Browserbase 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 Browserbase.
- 1
Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin - 2
Connect Browserbase
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Browserbase?"
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:
openclaw plugins install clawhub:clawlink-pluginThen 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 Browserbase in the ClawLink dashboard — paste your Browserbase API key once.
Verify the connection by asking OpenClaw:
Use Browserbase to download session artifacts 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:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Browserbase is connected in the dashboard, that agent calls the same 64 Browserbase tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Browserbase MCP for OpenClaw
Looking for a Browserbase MCP server for OpenClaw? ClawLink connects Browserbase to OpenClaw and exposes 64 Browserbase tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Browserbase integration works the same way.
What the OpenClaw Browserbase integration can do
64 Browserbase tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 64.
30 of 64 Browserbase tools for OpenClaw
| Tool | What it does |
|---|---|
Download session artifacts browserbase_tool_download_session_artifacts | Download a completed session's generated files as a ZIP archive |
Fetch page browserbase_tool_fetch_page | Fetch a page and return its content, headers, and metadata |
Get agent browserbase_tool_get_agent | Retrieve a reusable browser agent by its agentId |
Get certificate browserbase_tool_get_certificate | Retrieve a Browserbase certificate by its ID |
Get context browserbase_tool_get_context | Return metadata for a browser context by ID |
Get download browserbase_tool_get_download | Get a single download by ID as metadata or a downloadable file object |
Get extension browserbase_tool_get_extension | Retrieve details of a specific browser extension |
Get function browserbase_tool_get_function | Retrieve a Browserbase function by its ID |
Get function build browserbase_tool_get_function_build | Retrieve a Browserbase function build by its build ID |
Get function build logs browserbase_tool_get_function_build_logs | Retrieve Browserbase function build logs by the build ID |
Get function version browserbase_tool_get_function_version | Retrieve a Browserbase function version by its version ID |
Get invocation browserbase_tool_get_invocation | Retrieve a Browserbase function invocation by its invocation ID |
Get invocation logs browserbase_tool_get_invocation_logs | Retrieve Browserbase function invocation logs by the invocation ID |
Get keypair browserbase_tool_get_keypair | Retrieve the project's public HPKE encryption key and keypair ID |
Get project browserbase_tool_get_project | Return project metadata, default timeout, and assigned concurrency |
Get project usage browserbase_tool_get_project_usage | Retrieve usage statistics for a project including browser minutes and proxy bytes consumed |
Get run browserbase_tool_get_run | Retrieve a browser agent run's current status, result, and session details |
Get secret browserbase_tool_get_secret | Retrieve a project secret's ID and name by UUID, without its secret value |
Get session browserbase_tool_get_session | Return status, connection details, and timestamps for a browser session |
Get session debug URLS browserbase_tool_get_session_debug_urls | Return live debugger and WebSocket URLs for a running browser session |
Get session logs browserbase_tool_get_session_logs | Return network request and response events captured during a browser session |
Get session replay browserbase_tool_get_session_replay | Return HLS replay metadata and page playlist paths for a recorded session |
Get session replay page browserbase_tool_get_session_replay_page | Return the HLS M3U8 playlist for one recorded replay page |
Get webhook browserbase_tool_get_webhook | Retrieve a single webhook by ID, without its signing secret |
List agents browserbase_tool_list_agents | List one page of reusable browser agents across your account |
List certificates browserbase_tool_list_certificates | List Browserbase certificates with their IDs, timestamps, and project IDs |
List downloads browserbase_tool_list_downloads | List one page of download metadata for a required browser session |
List function builds browserbase_tool_list_function_builds | List one page of Browserbase function builds, optionally filtered by status |
List function secrets browserbase_tool_list_function_secrets | List one page of secret IDs and names attached to a Browserbase function, optionally filtered |
List function versions browserbase_tool_list_function_versions | List one page of versions for a Browserbase function by its UUID |
Try it: find the Browserbase tool you need
Browse the 30 Browserbase tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Use Browserbase to download session artifacts 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 OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Browserbase working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Browserbase API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Browserbase 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 Browserbase. | 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 Browserbase actions to the runtime in a format your agent can reliably use. | 64 tools for Browserbase are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Browserbase 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 Browserbase in the browser, and the 64 tools above work from chat. There is no SDK and no config file, and the Browserbase key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Browserbase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Browserbase, but the calls run through the ClawLink plugin and your connected account. Make sure Browserbase 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 Browserbase 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 Browserbase tools
Browserbase 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 Browserbase 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.
Browserbase 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 Browserbase has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Browserbase integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Browserbase: link your Browserbase account once in the browser and OpenClaw can call the Browserbase API through 64 ready-made tools — no custom code or token handling.
How do I add Browserbase to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Browserbase skill from ClawHub, then you click Connect in the dashboard to authorize Browserbase. OpenClaw calls the tools from the next message — no config files, and the Browserbase key you paste is stored server-side instead of in your environment.
How long does it take to connect Browserbase to OpenClaw?
About two minutes. Sign in, click Connect next to Browserbase in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Browserbase 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 Browserbase working from chat.
OpenClaw installed the Browserbase skill but can't call the tools
The ClawHub skill teaches OpenClaw about Browserbase, but the calls run through the ClawLink plugin and your connected account. Make sure Browserbase 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
OpenClaw DataRobot integration
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
OpenClaw ElevenLabs integration
Generate speech and voice cloning
Connect 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.