# How to connect Hyperbrowser to Hermes Agent (paste one key, 42 tools) > Connect Hyperbrowser to Hermes with ClawLink: paste your Hyperbrowser key once and 42 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/hyperbrowser Most guides for giving Hermes Agent Hyperbrowser 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 Hyperbrowser setup: pair once in the browser and your always-on Hermes agent can act on Hyperbrowser 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 Hyperbrowser. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Hyperbrowser** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent 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 hyperbrowser # connect Hyperbrowser (browser OAuth) npx -y @useclawlink/cli actions hyperbrowser # list available actions npx -y @useclawlink/cli run hyperbrowser --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Hyperbrowser in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Hyperbrowser API key once. Verify the connection by asking Hermes: > Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention. ### 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Hyperbrowser is connected in the dashboard, that agent calls the same 42 Hyperbrowser 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). ## Hyperbrowser MCP for Hermes Looking for a Hyperbrowser MCP server for Hermes Agent? ClawLink connects Hyperbrowser to Hermes Agent and exposes 42 Hyperbrowser 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 OpenClaw instead? The [OpenClaw Hyperbrowser integration](https://claw-link.dev/openclaw/hyperbrowser) works the same way. ## What the Hermes Agent Hyperbrowser integration can do 42 Hyperbrowser 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 42. ### 30 of 42 Hyperbrowser tools for Hermes | Tool | What it does | |---|---| | **Fetch web page** `hyperbrowser_fetch_web_page` | Fetch a web page and return content in various formats (HTML, Markdown, JSON, screenshot, etc.) | | **Get browser use task status** `hyperbrowser_get_browser_use_task_status` | Retrieve the current status of a browser-use task | | **Get claude computer use task result** `hyperbrowser_get_claude_computer_use_task_result` | Retrieve the complete result and status of a Claude Computer Use task | | **Get claude computer use task status** `hyperbrowser_get_claude_computer_use_task_status` | Poll the execution status of a Claude Computer Use task | | **Get crawl job status** `hyperbrowser_get_crawl_job_status` | Retrieve the status and results of a specific crawl job | | **Get crawl status** `hyperbrowser_get_crawl_status` | Retrieve the current status of a specific crawl job | | **Get cua task result** `hyperbrowser_get_cua_task_result` | Retrieve the status and results of a CUA (Claude User Agent) task | | **Get cua task status** `hyperbrowser_get_cua_task_status` | Poll the execution status of a CUA task | | **Get extract job result** `hyperbrowser_get_extract_job_result` | Fetch the status and results of a specific extract job | | **Get extract job status** `hyperbrowser_get_extract_job_status` | Retrieve the status of an extract job | | **Get gemini computer use task result** `hyperbrowser_get_gemini_computer_use_task_result` | Retrieve the current status and results of a Gemini Computer Use task | | **Get hyper agent task result** `hyperbrowser_get_hyper_agent_task_result` | Retrieve the status and results of a HyperAgent task | | **Get profile** `hyperbrowser_get_profile` | Retrieves details of a specific Hyperbrowser profile by its UUID | | **Get scrape job result** `hyperbrowser_get_scrape_job_result` | Retrieves the status and results of a scrape job | | **Get scrape job status** `hyperbrowser_get_scrape_job_status` | Retrieve the current status of a specific scrape job | | **Get session details** `hyperbrowser_get_session_details` | Retrieve detailed information about a Hyperbrowser session by its ID | | **Get session downloads URL** `hyperbrowser_get_session_downloads_url` | Retrieve the downloads URL for a session | | **Get session recording** `hyperbrowser_get_session_recording` | Retrieve the recording URL for a browser session | | **Get session video recording URL** `hyperbrowser_get_session_video_recording_url` | Retrieve the video recording URL for a browser session | | **Get web crawl result** `hyperbrowser_get_web_crawl_result` | Retrieve the status and results of a web crawl job | | **Get web crawl status** `hyperbrowser_get_web_crawl_status` | Retrieve just the status of a web crawl job without the full results | | **List extensions** `hyperbrowser_list_extensions` | List all browser extensions | | **List profiles** `hyperbrowser_list_profiles` | List profiles | | **List sessions** `hyperbrowser_list_sessions` | List sessions with optional status filter | | **Search web** `hyperbrowser_search_web` | Perform a web search and retrieve results with titles, URLs, and descriptions | | **Add extension** `hyperbrowser_add_extension` | Add a new browser extension to Hyperbrowser for use in sessions | | **Create profile** `hyperbrowser_create_profile` | Creates a new persistent Hyperbrowser profile for storing browser state (cookies, sessions | | **Create scrape job** `hyperbrowser_create_scrape_job` | Initiate a new scrape job | | **Create session** `hyperbrowser_create_session` | Create a new browser session with custom stealth, proxy, and privacy settings | | **Start browser use task** `hyperbrowser_start_browser_use_task` | Start an asynchronous browser-use task | ## Example prompts **Fetch Web Page** > Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention. **Get Browser Use Task Status** > Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention. **Get Claude Computer Use Task Result** > Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention. **Get Claude Computer Use Task Status** > Pull the relevant data from Hyperbrowser, 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 Hyperbrowser working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Hyperbrowser API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Hyperbrowser 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 Hyperbrowser. | 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 Hyperbrowser actions to the runtime in a format your agent can reliably use. | 42 tools for Hyperbrowser are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Hyperbrowser 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 Hyperbrowser in the browser, and the 42 tools above work from chat. There is no SDK and no config file, and the Hyperbrowser 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. ### Hermes paired but still can't use Hyperbrowser 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 Hyperbrowser 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 Hyperbrowser tools Hyperbrowser 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 Hyperbrowser 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. ### Hyperbrowser 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 Hyperbrowser has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Hyperbrowser integration? Yes. ClawLink is the fastest way to connect Hermes to Hyperbrowser: link your Hyperbrowser account once in the browser and Hermes Agent can call the Hyperbrowser API through 42 ready-made tools — no custom code or token handling. ### How do I connect Hyperbrowser 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 Hyperbrowser in the dashboard and Hermes can use it from the next message — no config files, and the Hyperbrowser key you paste is stored server-side instead of in your environment. ### How long does it take to connect Hyperbrowser to Hermes Agent? About two minutes. Sign in, click Connect next to Hyperbrowser in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Hyperbrowser 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 Hyperbrowser working from chat. ### Hermes paired but still can't use Hyperbrowser 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 - [DataRobot](https://claw-link.dev/hermes/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/hermes/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](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.