How to integrate Hyperbrowser MCP with LangChain

This guide walks you through connecting Hyperbrowser to LangChain 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 LangChain 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 LangChain 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 LangChain 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 Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Hyperbrowser project to Composio
  • Create a Tool Router MCP session for Hyperbrowser
  • Initialize an MCP client and retrieve Hyperbrowser tools
  • Build a LangChain agent that can interact with Hyperbrowser
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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 step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • 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 @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Hyperbrowser functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Hyperbrowser tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['hyperbrowser']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Hyperbrowser tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Hyperbrowser tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "hyperbrowser-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Hyperbrowser MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Hyperbrowser tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Hyperbrowser related question or task to the agent.\n");

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

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Hyperbrowser and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['hyperbrowser']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "hyperbrowser-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Hyperbrowser related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

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

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
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 Agent SDK logo

Claude Agent SDK

Use Hyperbrowser MCP with Claude Agent 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

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