How to integrate Hyperbrowser MCP with Claude Agent SDK

This guide walks you through connecting Hyperbrowser to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Hyperbrowser agent that can start a browser session with stealth mode, extract all product titles from this url, check status of your ongoing scrape job through natural language commands. This guide will help you understand how to give your Claude Agent SDK agent real control over a Hyperbrowser account through Composio's Hyperbrowser MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Hyperbrowser logoHyperbrowser
Api Key

Hyperbrowser is a next-generation platform for scalable browser automation. It empowers AI agents to interact with web apps, automate workflows, and handle browser sessions at scale.

42 Tools

Introduction

This guide walks you through connecting Hyperbrowser to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Hyperbrowser agent that can start a browser session with stealth mode, extract all product titles from this url, check status of your ongoing scrape job through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Hyperbrowser account through Composio's Hyperbrowser MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Hyperbrowser with

OpenAI Agents SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Hyperbrowser
  • Configure an AI agent that can use Hyperbrowser as a tool
  • Run a live chat session where you can ask the agent to perform Hyperbrowser operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Hyperbrowser account
  • Some knowledge of Python
2

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • @composio/core provides Composio integration for Anthropic
  • @anthropic-ai/claude-agent-sdk is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude
5

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The dotenv.config() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Hyperbrowser functionality
6

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Hyperbrowser
  const session = await composio.create(USER_ID, {
    toolkits: ['hyperbrowser'],
  });
  const mcpUrl = session?.mcp.url;
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Hyperbrowser
  • The returned url is the MCP server URL that your agent will use
7

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Hyperbrowser tools via Composio.',
  maxTurns: 10,
};
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Hyperbrowser
  • maxTurns: 10 limits the conversation length to prevent excessive API usage
8

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}
What's happening:
  • The readline interface is created to handle user input and output
  • The query function is used to send the user's input to the agent
  • The chat loop continues until the user types 'exit' or 'quit'
9

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}
What's happening:
  • The chat function is the entry point for the application
  • The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Hyperbrowser and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['hyperbrowser']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Hyperbrowser tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Hyperbrowser through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.
TOOLS

Supported Tools

Every Hyperbrowser action and event your agent gets out of the box.

Add Extension

Tool to add a new browser extension to Hyperbrowser for use in sessions.

Create Hyperbrowser Profile

Creates a new persistent Hyperbrowser profile for storing browser state (cookies, sessions, etc.

Create Scrape Job

Tool to initiate a new scrape job.

Create Session

Tool to create a new browser session with custom stealth, proxy, and privacy settings.

Delete Profile

Tool to delete a profile.

Fetch Web Page

Tool to fetch a web page and return content in various formats (HTML, Markdown, JSON, screenshot, etc.

Get browser-use task status

Tool to retrieve the current status of a browser-use task.

Get Claude Computer Use Task Result

Tool to retrieve the complete result and status of a Claude Computer Use task.

Get Claude Computer Use Task Status

Poll the execution status of a Claude Computer Use task.

Get Crawl Job Status

Tool to retrieve the status and results of a specific crawl job.

Get Crawl Status

Tool to retrieve the current status of a specific crawl job.

Get CUA Task Result

Tool to retrieve the status and results of a CUA (Claude User Agent) task.

Get CUA Task Status

Poll the execution status of a CUA task.

Get Extract Job Result

Tool to fetch the status and results of a specific extract job.

Get Extract Job Status

Retrieve the status of an extract job.

Get Gemini Computer Use task result

Tool to retrieve the current status and results of a Gemini Computer Use task.

Get HyperAgent Task Result

Tool to retrieve the status and results of a HyperAgent task.

Get Profile By ID

Retrieves details of a specific Hyperbrowser profile by its UUID.

Get Scrape Job Result

Retrieves the status and results of a scrape job.

Get Scrape Job Status

Tool to retrieve the current status of a specific scrape job.

Get Session Details

Retrieve detailed information about a Hyperbrowser session by its ID.

Get Session Downloads URL

Tool to retrieve the downloads URL for a session.

Get Session Recording

Retrieve the recording URL for a browser session.

Get Session Video Recording URL

Tool to retrieve the video recording URL for a browser session.

Get Web Crawl Result

Tool to retrieve the status and results of a web crawl job.

Get Web Crawl Status

Tool to retrieve just the status of a web crawl job without the full results.

List Extensions

Tool to list all browser extensions.

List Profiles

Tool to list profiles.

List Sessions

Tool to list sessions with optional status filter.

Search Web

Tool to perform a web search and retrieve results with titles, URLs, and descriptions.

Start Browser Use Task

Tool to start an asynchronous browser-use task.

Start Claude Computer Use Task

Tool to start a Claude Computer Use task.

Start Crawl Job

Tool to start a new crawl job for a specified URL.

Start CUA Task

Tool to start an OpenAI CUA (Computer-Using Agent) task.

Start Extract Job

Start an AI-powered data extraction job from one or more web pages.

Start Gemini Computer Use Task

Tool to start a Gemini Computer Use task for browser automation using Google's Gemini.

Start Web Crawl

Tool to start an asynchronous web crawl job that follows links from a starting URL and returns content from each page.

Stop Browser Use Task

Tool to stop a running browser-use task.

Stop Claude Computer Use Task

Tool to stop a running Claude computer use task.

Stop CUA Task

Tool to stop a running CUA task.

Stop Gemini Computer Use Task

Tool to stop a running Gemini computer use task.

Stop Session

Tool to stop a running session by ID.

FRAMEWORKS

How to build Hyperbrowser MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Hyperbrowser MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Hyperbrowser MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Hyperbrowser MCP with Claude Cowork

Codex logo

Codex

Use Hyperbrowser MCP with Codex

OpenClaw logo

OpenClaw

Use Hyperbrowser MCP with OpenClaw

Hermes logo

Hermes

Use Hyperbrowser MCP with Hermes

CLI logo

CLI

Use Hyperbrowser MCP with CLI

Google ADK logo

Google ADK

Use Hyperbrowser MCP with Google ADK

LangChain logo

LangChain

Use Hyperbrowser MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Hyperbrowser MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Hyperbrowser MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Hyperbrowser MCP with LlamaIndex

CrewAI logo

CrewAI

Use Hyperbrowser MCP with CrewAI

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Hyperbrowser.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Hyperbrowser tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies