# How to connect Anchor Browser to OpenClaw (paste one key, 64 tools) > Connect Anchor Browser to OpenClaw with ClawLink: paste your Anchor Browser key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/anchor-browser The usual route to Anchor Browser 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 Anchor Browser setup: install one ClawHub skill, connect Anchor Browser in the browser, and OpenClaw can call real Anchor Browser 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 Anchor Browser. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Anchor Browser** — 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 anchor-browser # connect Anchor Browser (browser OAuth) npx -y @useclawlink/cli actions anchor-browser # list available actions npx -y @useclawlink/cli run anchor-browser --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 Anchor Browser in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Anchor Browser API key once. Verify the connection by asking OpenClaw: > Use Anchor Browser to copy selected text 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 Anchor Browser is connected in the dashboard, that agent calls the same 64 Anchor Browser 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). ## Anchor Browser MCP for OpenClaw Looking for a Anchor Browser MCP server for OpenClaw? ClawLink connects Anchor Browser to OpenClaw and exposes 64 Anchor Browser 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 Anchor Browser integration](https://claw-link.dev/hermes/anchor-browser) works the same way. ## What the OpenClaw Anchor Browser integration can do 64 Anchor Browser 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 Anchor Browser tools for OpenClaw | Tool | What it does | |---|---| | **Copy selected text** `anchor_browser_copy_selected_text` | Copy currently selected text in a browser session to the clipboard | | **Get batch session status** `anchor_browser_get_batch_session_status` | Retrieve detailed status information for a specific batch including progress and errors | | **Get browser session** `anchor_browser_get_browser_session` | Retrieve detailed information about a specific browser session | | **Get clipboard content** `anchor_browser_get_clipboard_content` | Retrieve the current content of the clipboard from a browser session | | **Get latest task version** `anchor_browser_get_latest_task_version` | Retrieve the latest version of a task including the full base64 encoded code content | | **Get profile2** `anchor_browser_get_profile2` | Retrieve details of a specific profile by its name | | **Get session pages** `anchor_browser_get_session_pages` | Retrieve all pages associated with a specific browser session | | **Get task draft** `anchor_browser_get_task_draft` | Retrieve the draft version of a task, including the full Base64 encoded code content | | **Get task execution result** `anchor_browser_get_task_execution_result` | Retrieve a single task execution result by its ID | | **Get task metadata** `anchor_browser_get_task_metadata` | Retrieve task metadata without downloading the full task code | | **Get task version** `anchor_browser_get_task_version` | Retrieve a specific version of a task, including the full code content | | **Get webpage content** `anchor_browser_get_webpage_content` | Retrieve rendered content of a webpage in HTML or Markdown format | | **List agent resources** `anchor_browser_list_agent_resources` | List all agent resources (files) uploaded to a browser session | | **List extensions** `anchor_browser_list_extensions` | Retrieves all browser extensions uploaded by the authenticated user | | **List integrations** `anchor_browser_list_integrations` | Retrieve all integrations for the authenticated team | | **List profiles** `anchor_browser_list_profiles` | Fetch all stored browser profiles | | **List session downloads** `anchor_browser_list_session_downloads` | Retrieve metadata of files downloaded during a browser session | | **List session recordings** `anchor_browser_list_session_recordings` | List all recordings for a specific browser session | | **List sessions** `anchor_browser_list_sessions` | List all browser sessions | | **List task executions** `anchor_browser_list_task_executions` | Retrieve execution history for a specific task with filtering and pagination support | | **List task versions** `anchor_browser_list_task_versions` | Retrieve all versions of a specific task, including draft and published versions | | **List tasks** `anchor_browser_list_tasks` | Retrieve a paginated list of all tasks for the authenticated team | | **Screenshot webpage** `anchor_browser_screenshot_webpage` | Take a screenshot of a specified webpage within a session | | **Take screenshot** `anchor_browser_take_screenshot` | Take a screenshot of the current browser session and return it as an image | | **Wait for event** `anchor_browser_wait_for_event` | Blocks execution until a specific named event is signaled or the timeout expires | | **Click mouse** `anchor_browser_click_mouse` | Perform a mouse click at specified coordinates within a browser session | | **Create integration** `anchor_browser_create_integration` | Create a new integration with a third-party service like 1Password | | **Create or update task draft** `anchor_browser_create_or_update_task_draft` | Create or update the draft version of a task | | **Create profile** `anchor_browser_create_profile` | Creates a new browser profile from an active session | | **Create task** `anchor_browser_create_task` | Create a new task or update an existing task with the same name | ## Example prompts **Copy Selected Text** > Use Anchor Browser to copy selected text and walk me through the result in plain English. **Get Batch Session Status** > Pull the relevant data from Anchor Browser, summarize it in plain English, and point out anything that needs attention. **Get Browser Session** > Pull the relevant data from Anchor Browser, summarize it in plain English, and point out anything that needs attention. **Get Clipboard Content** > Pull the relevant data from Anchor Browser, 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 Anchor Browser working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Anchor Browser API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Anchor Browser 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 Anchor Browser. | 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 Anchor Browser actions to the runtime in a format your agent can reliably use. | 64 tools for Anchor Browser are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Anchor Browser 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 Anchor Browser in the browser, and the 64 tools above work from chat. There is no SDK and no config file, and the Anchor Browser 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 Anchor Browser skill but can't call the tools The ClawHub skill teaches OpenClaw about Anchor Browser, but the calls run through the ClawLink plugin and your connected account. Make sure Anchor Browser 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 Anchor Browser 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 Anchor Browser tools Anchor Browser 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 Anchor Browser 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. ### Anchor Browser 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 Anchor Browser has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Anchor Browser integration? Yes. ClawLink is the fastest way to connect OpenClaw to Anchor Browser: link your Anchor Browser account once in the browser and OpenClaw can call the Anchor Browser API through 64 ready-made tools — no custom code or token handling. ### How do I add Anchor Browser to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Anchor Browser skill from ClawHub, then you click Connect in the dashboard to authorize Anchor Browser. OpenClaw calls the tools from the next message — no config files, and the Anchor Browser key you paste is stored server-side instead of in your environment. ### How long does it take to connect Anchor Browser to OpenClaw? About two minutes. Sign in, click Connect next to Anchor Browser in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Anchor Browser 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 Anchor Browser working from chat. ### OpenClaw installed the Anchor Browser skill but can't call the tools The ClawHub skill teaches OpenClaw about Anchor Browser, but the calls run through the ClawLink plugin and your connected account. Make sure Anchor Browser 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 tools](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. - [OpenClaw Just One API integration](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.