How to integrate Hyperbrowser MCP with Hermes

Hyperbrowser logo
Hermes logo
divider

Introduction

Hermes is a 24/7 autonomous agent that lives on your computer or server — it remembers what it learns and evolves as your usage grows.

This guide explains the easiest and most robust way to connect your Hyperbrowser account to Hermes. You can do this through either Composio Connect CLI or Composio Connect MCP. For personal use we recommend the CLI, but you won't go wrong with MCP either.

Also integrate Hyperbrowser with

What is Composio Connect?

Composio Connect is a consumer offering that lets anyone plug 1,000+ applications directly into their agent harness — including Hermes. It can:

  • Search and load tools from relevant toolkits on-demand, reducing context usage.
  • Chain multiple tools to accomplish complex workflows via a remote workbench, without excessive back-and-forth with the LLM.
  • Manage app authentication end-to-end with zero manual overhead.

Integrating Hyperbrowser with Hermes

Using Composio Connect CLI

1. Install the Composio CLI

Run the install script directly, or paste https://composio.dev/hermes into your Hermes chat box to have it installed for you.

bash
curl -fsSL https://composio.dev/install | bash
Hermes authenticating with Composio

2. Authenticate

Once the CLI is installed, ask Hermes to authenticate with Composio.

3. Connect to Hyperbrowser

Ask your agent to connect to Hyperbrowser, or simply request any Hyperbrowser-related task. Hermes will prompt you to authenticate and authorize access.

4. Done. You're all set with a new Hyperbrowser connection.


Using Composio Connect MCP

1. Get your MCP URL and API Key

Go to dashboard.composio.dev and copy your Connect MCP URL and API key.

Copy MCP URL and API key from Composio dashboard

2. Open the Hermes config file

bash
nano ~/.hermes/config.yaml

3. Add the Composio Connect MCP server

bash
mcp_servers:
  composio:
    url: "https://connect.composio.dev/mcp"
    headers:
      x-consumer-api-key: "YOUR_COMPOSIO_API_KEY"
    connect_timeout: 60
    timeout: 180

Save with Ctrl + O, Enter, then exit with Ctrl + X.

4. Restart your Hermes agent

Once restarted, ask your agent to connect to Hyperbrowser or request any Hyperbrowser-related task. It will prompt you to authenticate and authorize access.

5. Done!

What is the Hyperbrowser MCP server, and what's possible with it?

The Hyperbrowser MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Hyperbrowser account. It provides structured and secure access to automated browser sessions, web scraping, and browser-based task management, so your agent can launch sessions, extract data, manage automation jobs, and monitor progress on your behalf.

  • Automated browser session creation: Let your agent spin up new browser sessions with custom privacy, stealth, and proxy settings for tailored automation tasks.
  • Scalable web scraping and extraction: Easily initiate and manage scrape jobs to extract structured content from any target website, with support for session and scrape customization.
  • Real-time job status monitoring: Have your agent check, track, and report the live status of browser-use, crawl, or data extraction jobs, ensuring you always know what's happening.
  • Retrieve results from automation jobs: Fetch and review the outputs of completed crawl or extract jobs, including paginated data and detailed results, right inside your workflow.
  • Profile and automation management: Create or delete Hyperbrowser profiles as needed, giving you flexible control over your automation environment and resources.

Supported Tools & Triggers

Tools
Create Hyperbrowser ProfileTool to create a new profile.
Create Scrape JobTool to initiate a new scrape job.
Create SessionTool to create a new browser session with custom stealth, proxy, and privacy settings.
Delete ProfileTool to delete a profile.
Get browser-use task statusTool to retrieve the current status of a browser-use task.
Get Claude Computer Use Task StatusTool to retrieve the status of a Claude Computer Use task.
Get Crawl Job ResultTool to retrieve the result of a completed crawl job.
Get Crawl Job StatusTool to retrieve the status and results of a specific crawl job.
Get Extract Job ResultTool to fetch the status and results of a specific extract job.
Get Extract Job StatusTool to retrieve the status of an extract job.
Get Profile By IDTool to retrieve profile details by ID.
Get Scrape Job ResultTool to fetch the status and results of a specific scrape job.
Get Scrape Job StatusTool to retrieve the current status of a specific scrape job.
Get Session DetailsTool to retrieve session details by ID.
Get Session Downloads URLTool to retrieve the downloads URL for a session.
Get Session RecordingTool to retrieve the recording URL of a session.
List ProfilesTool to list profiles.
List SessionsTool to list sessions with optional status filter.
Start Browser Use TaskTool to start an asynchronous browser-use task.
Start Claude Computer Use TaskTool to start a Claude Computer Use task.
Start Crawl JobTool to start a new crawl job for a specified URL.
Start Extract JobTool to start an extract job.
Stop Browser Use TaskTool to stop a running browser-use task.
Stop Claude Computer Use TaskTool to stop a running Claude computer use task.
Stop SessionTool to stop a running session by ID.

Way Forward

With Hyperbrowser connected, Hermes can now act on your behalf whenever it detects a relevant task or you ask it to.

From here, you can extend Hermes further:

  • Connect more apps: Calendar, Slack, Notion, Linear, and hundreds of others are available through the same Composio Connect setup. Each new integration compounds what Hermes can do for you.
  • Build workflows across tools: Once multiple apps are connected, Hermes can chain actions together — turn an email into a calendar invite, a Slack message into a Linear ticket, or a meeting note into a follow-up draft.
  • Let it learn your patterns: The more you use Hermes, the better it gets at anticipating how you'd handle recurring tasks. Give it feedback on drafts and decisions, and it will adapt.

If you run into trouble or want to share what you've built, join the community or check out the Docs for deeper configuration options.

How to build Hyperbrowser MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Hyperbrowser MCP?

With a standalone Hyperbrowser MCP server, the agents and LLMs can only access a fixed set of Hyperbrowser tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Hyperbrowser and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Hermes?

Yes, you can. Hermes fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Hyperbrowser tools.

Can I manage the permissions and scopes for Hyperbrowser while using Tool Router?

Yes, absolutely. You can configure which Hyperbrowser scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Hyperbrowser data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.