How to integrate Hyperbrowser MCP with OpenAI Agents SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Hyperbrowser Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Hyperbrowser to the OpenAI Agents 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 my ongoing scrape job, delete an unused hyperbrowser profile through natural language commands.

This guide will help you understand how to give your OpenAI Agents 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.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI 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 open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

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.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Hyperbrowser project
  • Some knowledge of Python or Typescript

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

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Hyperbrowser.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Hyperbrowser Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["hyperbrowser"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only hyperbrowser.
  • The router checks the user's Hyperbrowser connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Hyperbrowser.
  • This approach keeps things lightweight and lets the agent request Hyperbrowser tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Hyperbrowser. "
        "Help users perform Hyperbrowser operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Hyperbrowser and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Hyperbrowser operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Hyperbrowser.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Hyperbrowser and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["hyperbrowser"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Hyperbrowser. "
        "Help users perform Hyperbrowser operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Hyperbrowser MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Hyperbrowser.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Hyperbrowser MCP Agent with another framework

Claude Agent SDK

Claude Agent SDK

Use Hyperbrowser MCP with Claude Agent SDK

Google ADK

Google ADK

Use Hyperbrowser MCP with Google ADK

LangChain

LangChain

Use Hyperbrowser MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Hyperbrowser MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Hyperbrowser MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Hyperbrowser MCP with LlamaIndex

CrewAI

CrewAI

Use Hyperbrowser MCP with CrewAI

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 OpenAI Agents SDK?

Yes, you can. OpenAI Agents 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.

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
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.

Book a call↗Get started for free