How to connect Anchor Browser to Hermes Agent
Connect Anchor Browser to Hermes with ClawLink: paste your Anchor Browser key once and 64 tools work from chat. No MCP server to run, nothing stored on your machine.
Anchor BrowserAPI KEYMCPAnchor Browser is a developer platform that enables AI agents to interact with the web through browser automation, transforming complex web interactions into simple API endpoints.. Once connected, Hermes Agent can read and act on Anchor Browser from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Anchor Browser 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 Anchor Browser setup: pair once in the browser and your always-on Hermes agent can act on Anchor Browser 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 Anchor Browser.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Anchor Browser
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Anchor Browser?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
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 testThen connect Anchor Browser in the ClawLink dashboard — paste your Anchor Browser API key once.
Verify the connection by asking Hermes:
Use Anchor Browser to copy selected text and walk me through the result in plain English.
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:
npx -y @useclawlink/cli loginlogin 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.
Anchor Browser MCP for Hermes
Looking for a Anchor Browser MCP server for Hermes Agent? ClawLink connects Anchor Browser to Hermes Agent and exposes 64 Anchor Browser tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Anchor Browser integration works the same way.
What the Hermes Agent Anchor Browser integration can do
64 Anchor Browser tools are ready for Hermes Agent 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 Hermes
| 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 |
Try it: find the Anchor Browser tool you need
Browse the 30 Anchor Browser tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Anchor Browser to copy selected text and walk me through the result in plain English.
Pull the relevant data from Anchor Browser, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Anchor Browser, summarize it in plain English, and point out anything that needs attention.
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 Hermes Agent. 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 Hermes Agent 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 comparison.
Troubleshooting
Hermes paired but still can't use Anchor Browser
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 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.
FAQ
Is there a Hermes Agent Anchor Browser integration?
Yes. ClawLink is the fastest way to connect Hermes to Anchor Browser: link your Anchor Browser account once in the browser and Hermes Agent can call the Anchor Browser API through 64 ready-made tools — no custom code or token handling.
How do I connect Anchor Browser 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 Anchor Browser in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Anchor Browser in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Anchor Browser working from chat.
Hermes paired but still can't use Anchor Browser
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
Connect DataRobot
DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
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.
Hermes Just One API integration
Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.