ClawLink

How to connect Hyperbrowser to Hermes Agent

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.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Hyperbrowser
Hyperbrowser
HyperbrowserAPI KEYMCP

Hyperbrowser is a next-generation platform empowering AI agents and enabling effortless, scalable browser automation.. Once connected, Hermes Agent can read and act on Hyperbrowser from chat — pairing, token refresh, and tool wiring handled for you.

42 tools

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. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Hyperbrowser

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Hyperbrowser?"

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 test

Then connect Hyperbrowser in the ClawLink 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:

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.

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, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Hyperbrowser integration 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

ToolWhat it does
Fetch web page hyperbrowser_fetch_web_pageFetch a web page and return content in various formats (HTML, Markdown, JSON, screenshot, etc.)
Get browser use task status hyperbrowser_get_browser_use_task_statusRetrieve the current status of a browser-use task
Get claude computer use task result hyperbrowser_get_claude_computer_use_task_resultRetrieve the complete result and status of a Claude Computer Use task
Get claude computer use task status hyperbrowser_get_claude_computer_use_task_statusPoll the execution status of a Claude Computer Use task
Get crawl job status hyperbrowser_get_crawl_job_statusRetrieve the status and results of a specific crawl job
Get crawl status hyperbrowser_get_crawl_statusRetrieve the current status of a specific crawl job
Get cua task result hyperbrowser_get_cua_task_resultRetrieve the status and results of a CUA (Claude User Agent) task
Get cua task status hyperbrowser_get_cua_task_statusPoll the execution status of a CUA task
Get extract job result hyperbrowser_get_extract_job_resultFetch the status and results of a specific extract job
Get extract job status hyperbrowser_get_extract_job_statusRetrieve the status of an extract job
Get gemini computer use task result hyperbrowser_get_gemini_computer_use_task_resultRetrieve the current status and results of a Gemini Computer Use task
Get hyper agent task result hyperbrowser_get_hyper_agent_task_resultRetrieve the status and results of a HyperAgent task
Get profile hyperbrowser_get_profileRetrieves details of a specific Hyperbrowser profile by its UUID
Get scrape job result hyperbrowser_get_scrape_job_resultRetrieves the status and results of a scrape job
Get scrape job status hyperbrowser_get_scrape_job_statusRetrieve the current status of a specific scrape job
Get session details hyperbrowser_get_session_detailsRetrieve detailed information about a Hyperbrowser session by its ID
Get session downloads URL hyperbrowser_get_session_downloads_urlRetrieve the downloads URL for a session
Get session recording hyperbrowser_get_session_recordingRetrieve the recording URL for a browser session
Get session video recording URL hyperbrowser_get_session_video_recording_urlRetrieve the video recording URL for a browser session
Get web crawl result hyperbrowser_get_web_crawl_resultRetrieve the status and results of a web crawl job
Get web crawl status hyperbrowser_get_web_crawl_statusRetrieve just the status of a web crawl job without the full results
List extensions hyperbrowser_list_extensionsList all browser extensions
List profiles hyperbrowser_list_profilesList profiles
List sessions hyperbrowser_list_sessionsList sessions with optional status filter
Search web hyperbrowser_search_webPerform a web search and retrieve results with titles, URLs, and descriptions
Add extension hyperbrowser_add_extensionAdd a new browser extension to Hyperbrowser for use in sessions
Create profile hyperbrowser_create_profileCreates a new persistent Hyperbrowser profile for storing browser state (cookies, sessions
Create scrape job hyperbrowser_create_scrape_jobInitiate a new scrape job
Create session hyperbrowser_create_sessionCreate a new browser session with custom stealth, proxy, and privacy settings
Start browser use task hyperbrowser_start_browser_use_taskStart an asynchronous browser-use task

Try it: find the Hyperbrowser tool you need

Browse the 30 Hyperbrowser tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Hyperbrowser, summarize it in plain English, and point out anything that needs attention.

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.

ManualClawLink
Credential handlingCollect, 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 maintenanceYou 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 usabilityYou 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.

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 comparison.

Troubleshooting

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.

FAQ

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.