# How to integrate Hyperbrowser MCP with Mastra AI

```json
{
  "title": "How to integrate Hyperbrowser MCP with Mastra AI",
  "toolkit": "Hyperbrowser",
  "toolkit_slug": "hyperbrowser",
  "framework": "Mastra AI",
  "framework_slug": "mastra-ai",
  "url": "https://composio.dev/toolkits/hyperbrowser/framework/mastra-ai",
  "markdown_url": "https://composio.dev/toolkits/hyperbrowser/framework/mastra-ai.md",
  "updated_at": "2026-05-06T08:16:05.497Z"
}
```

## Introduction

This guide walks you through connecting Hyperbrowser to Mastra AI 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 Mastra AI 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 SDK](https://composio.dev/toolkits/hyperbrowser/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hyperbrowser/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hyperbrowser/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hyperbrowser/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hyperbrowser/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hyperbrowser/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hyperbrowser/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hyperbrowser/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hyperbrowser/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/hyperbrowser/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/hyperbrowser/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/hyperbrowser/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/hyperbrowser/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Set up your environment so Mastra, OpenAI, and Composio work together
- Create a Tool Router session in Composio that exposes Hyperbrowser tools
- Connect Mastra's MCP client to the Composio generated MCP URL
- Fetch Hyperbrowser tool definitions and attach them as a toolset
- Build a Mastra agent that can reason, call tools, and return structured results
- Run an interactive CLI where you can chat with your Hyperbrowser agent

## What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.
Key features include:
- MCP Client: Built-in support for Model Context Protocol servers
- Toolsets: Organize tools into logical groups
- Step Callbacks: Monitor and debug agent execution
- OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

## 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

| Tool slug | Name | Description |
|---|---|---|
| `HYPERBROWSER_CREATE_PROFILE` | Create Hyperbrowser Profile | Tool to create a new profile. Use when you need to initialize a Hyperbrowser profile before analysis. |
| `HYPERBROWSER_CREATE_SCRAPE_JOB` | Create Scrape Job | Tool to initiate a new scrape job. Use when you need to extract structured content from a target URL with custom session and scrape settings. |
| `HYPERBROWSER_CREATE_SESSION` | Create Session | Tool to create a new browser session with custom stealth, proxy, and privacy settings. Use when initializing an automated browsing session with specific configuration. |
| `HYPERBROWSER_DELETE_PROFILE` | Delete Profile | Tool to delete a profile. Use when you need to remove a profile by its unique identifier after confirming its existence. |
| `HYPERBROWSER_GET_BROWSER_USE_TASK_STATUS` | Get browser-use task status | Tool to retrieve the current status of a browser-use task. Use when checking if a browser automation task has completed or is still pending. |
| `HYPERBROWSER_GET_CLAUDE_COMPUTER_USE_TASK_STATUS` | Get Claude Computer Use Task Status | Tool to retrieve the status of a Claude Computer Use task. Use after creating a task to poll its status. |
| `HYPERBROWSER_GET_CRAWL_JOB_RESULT` | Get Crawl Job Result | Tool to retrieve the result of a completed crawl job. Use after confirming crawl job completion to fetch current page batch and status. Supports pagination via page and batchSize. |
| `HYPERBROWSER_GET_CRAWL_JOB_STATUS` | Get Crawl Job Status | Tool to retrieve the status and results of a specific crawl job. Use after submitting a crawl job to check its progress or fetch results. |
| `HYPERBROWSER_GET_EXTRACT_JOB_RESULT` | Get Extract Job Result | Tool to fetch the status and results of a specific extract job. Use after initiating an extract job to monitor progress and retrieve final data. |
| `HYPERBROWSER_GET_EXTRACT_JOB_STATUS` | Get Extract Job Status | Tool to retrieve the status of an extract job. Use after submitting an extract job to poll its status. |
| `HYPERBROWSER_GET_PROFILE_BY_ID` | Get Profile By ID | Tool to retrieve profile details by ID. Use after confirming the profile ID. |
| `HYPERBROWSER_GET_SCRAPE_JOB_RESULT` | Get Scrape Job Result | Tool to fetch the status and results of a specific scrape job. Use after initiating a scrape job to monitor its progress and retrieve final data. |
| `HYPERBROWSER_GET_SCRAPE_JOB_STATUS` | Get Scrape Job Status | Tool to retrieve the current status of a specific scrape job. Use after initiating a scrape job to poll its status. |
| `HYPERBROWSER_GET_SESSION_DETAILS` | Get Session Details | Tool to retrieve session details by ID. Use after confirming the session ID. |
| `HYPERBROWSER_GET_SESSION_DOWNLOADS_URL` | Get Session Downloads URL | Tool to retrieve the downloads URL for a session. Use when you need the signed URL for session downloads after processing is complete. |
| `HYPERBROWSER_GET_SESSION_RECORDING` | Get Session Recording | Tool to retrieve the recording URL of a session. Use after confirming the session ID and when the recording is expected to be ready. |
| `HYPERBROWSER_LIST_PROFILES` | List Profiles | Tool to list profiles. Use when you need to fetch paginated profiles and optionally filter by name. |
| `HYPERBROWSER_LIST_SESSIONS` | List Sessions | Tool to list sessions with optional status filter. Use when you need a paginated overview of browser sessions before acting on them. |
| `HYPERBROWSER_START_BROWSER_USE_TASK` | Start Browser Use Task | Tool to start an asynchronous browser-use task. Use when you need to automate web interactions given a task instruction. |
| `HYPERBROWSER_START_CLAUDE_COMPUTER_USE_TASK` | Start Claude Computer Use Task | Tool to start a Claude Computer Use task. Use when you need AI-driven automated browser interactions. Call after you have your task prompt and any session preferences configured. |
| `HYPERBROWSER_START_CRAWL_JOB` | Start Crawl Job | Tool to start a new crawl job for a specified URL. Use when you need to initiate a web crawl before checking job status. |
| `HYPERBROWSER_START_EXTRACT_JOB` | Start Extract Job | Tool to start an extract job. Use when you need to initiate a new extraction with custom prompts, schema, and session options. Call after preparing URLs and desired extraction schema. |
| `HYPERBROWSER_STOP_BROWSER_USE_TASK` | Stop Browser Use Task | Tool to stop a running browser-use task. Use when halting an in-progress browser automation task after confirming its task ID. |
| `HYPERBROWSER_STOP_CLAUDE_COMPUTER_USE_TASK` | Stop Claude Computer Use Task | Tool to stop a running Claude computer use task. Use when a Claude computer use task is in progress and needs to be terminated. |
| `HYPERBROWSER_STOP_SESSION` | Stop Session | Tool to stop a running session by ID. Use after confirming the session is active. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Hyperbrowser MCP server is an implementation of the Model Context Protocol that connects your AI agent to Hyperbrowser. It provides structured and secure access so your agent can perform Hyperbrowser operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

Before starting, make sure you have:
- Node.js 18 or higher
- A Composio account with an active API key
- An OpenAI API key
- Basic familiarity with TypeScript

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key.
- You need credits or a connected billing setup to use the models.
- Store the key somewhere safe.
Composio API Key
- Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Go to Settings and copy your API key.
- This key lets your Mastra agent talk to Composio and reach Hyperbrowser through MCP.

### 2. Install dependencies

Install the required packages.
What's happening:
- @composio/core is the Composio SDK for creating MCP sessions
- @mastra/core provides the Agent class
- @mastra/mcp is Mastra's MCP client
- @ai-sdk/openai is the model wrapper for OpenAI
- dotenv loads environment variables from .env
```bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv
```

### 3. Set up environment variables

Create a .env file in your project root.
What's happening:
- COMPOSIO_API_KEY authenticates your requests to Composio
- COMPOSIO_USER_ID tells Composio which user this session belongs to
- OPENAI_API_KEY lets the Mastra agent call OpenAI models
```bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here
```

### 4. Import libraries and validate environment

What's happening:
- dotenv/config auto loads your .env so process.env.* is available
- openai gives you a Mastra compatible model wrapper
- Agent is the Mastra agent that will call tools and produce answers
- MCPClient connects Mastra to your Composio MCP server
- Composio is used to create a Tool Router session
```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
```

### 5. Create a Tool Router session for Hyperbrowser

What's happening:
- create spins up a short-lived MCP HTTP endpoint for this user
- The toolkits array contains "hyperbrowser" for Hyperbrowser access
- session.mcp.url is the MCP URL that Mastra's MCPClient will connect to
```typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["hyperbrowser"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Hyperbrowser MCP URL:", composioMCPUrl);
```

### 6. Configure Mastra MCP client and fetch tools

What's happening:
- MCPClient takes an id for this client and a list of MCP servers
- The headers property includes the x-api-key for authentication
- getTools fetches the tool definitions exposed by the Hyperbrowser toolkit
```typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
```

### 7. Create the Mastra agent

What's happening:
- Agent is the core Mastra agent
- name is just an identifier for logging and debugging
- instructions guide the agent to use tools instead of only answering in natural language
- model uses openai("gpt-5") to configure the underlying LLM
```typescript
const agent = new Agent({
    name: "hyperbrowser-mastra-agent",
    instructions: "You are an AI agent with Hyperbrowser tools via Composio.",
    model: "openai/gpt-5",
  });
```

### 8. Set up interactive chat interface

What's happening:
- messages keeps the full conversation history in Mastra's expected format
- agent.generate runs the agent with conversation history and Hyperbrowser toolsets
- maxSteps limits how many tool calls the agent can take in a single run
- onStepFinish is a hook that prints intermediate steps for debugging
```typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

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

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;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        hyperbrowser: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

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

## Complete Code

```typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["hyperbrowser"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      hyperbrowser: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "hyperbrowser-mastra-agent",
    instructions: "You are an AI agent with Hyperbrowser tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

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

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { hyperbrowser: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();
```

## Conclusion

You've built a Mastra AI agent that can interact with Hyperbrowser through Composio's Tool Router.
You can extend this further by:
- Adding other toolkits like Gmail, Slack, or GitHub
- Building a web-based chat interface around this agent
- Using multiple MCP endpoints to enable cross-app workflows

## How to build Hyperbrowser MCP Agent with another framework

- [OpenAI Agents SDK](https://composio.dev/toolkits/hyperbrowser/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/hyperbrowser/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/hyperbrowser/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/hyperbrowser/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/hyperbrowser/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/hyperbrowser/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/hyperbrowser/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/hyperbrowser/framework/cli)
- [Google ADK](https://composio.dev/toolkits/hyperbrowser/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/hyperbrowser/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/hyperbrowser/framework/ai-sdk)
- [LlamaIndex](https://composio.dev/toolkits/hyperbrowser/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/hyperbrowser/framework/crew-ai)

## Related Toolkits

- [Apilio](https://composio.dev/toolkits/apilio) - Apilio is a home automation platform that lets you connect and control smart devices from different brands. It helps you build flexible automations with complex conditions, schedules, and integrations.
- [Basin](https://composio.dev/toolkits/basin) - Basin is a no-code form backend for quickly setting up reliable contact forms. It lets you collect and manage form submissions without writing any server-side code.
- [Bouncer](https://composio.dev/toolkits/bouncer) - Bouncer is an email validation platform that verifies the authenticity of email addresses in real-time and batch. It helps boost deliverability and reduce bounce rates for your communications.
- [Conveyor](https://composio.dev/toolkits/conveyor) - Conveyor is a platform that automates security reviews with a Trust Center and AI-driven questionnaire automation. It streamlines compliance and vendor security processes for faster, hassle-free reviews.
- [Crowdin](https://composio.dev/toolkits/crowdin) - Crowdin is a localization management platform that streamlines translation workflows and collaboration. It helps teams centralize multilingual content, boost productivity, and automate translation processes.
- [Databox](https://composio.dev/toolkits/databox) - Databox is a business analytics platform that connects your data from any tool and device. It helps you track KPIs, build dashboards, and discover actionable insights.
- [Detrack](https://composio.dev/toolkits/detrack) - Detrack is a delivery management platform for real-time tracking and proof of delivery. It helps businesses automate notifications and keep customers updated every step of the way.
- [Dnsfilter](https://composio.dev/toolkits/dnsfilter) - Dnsfilter is a cloud-based DNS security and content filtering solution. It helps organizations block online threats and manage safe internet access with ease.
- [Faraday](https://composio.dev/toolkits/faraday) - Faraday lets you embed AI in workflows across your stack for smarter automation. It boosts your favorite tools with actionable intelligence and seamless integration.
- [Feathery](https://composio.dev/toolkits/feathery) - Feathery is an AI-powered platform for building dynamic data intake forms with advanced logic. It helps teams automate complex workflows and collect structured data with ease.
- [Fillout forms](https://composio.dev/toolkits/fillout_forms) - Fillout forms is an online platform for building and managing forms with a flexible API. It lets you create, distribute, and collect responses from forms with ease.
- [Formdesk](https://composio.dev/toolkits/formdesk) - Formdesk is an online form builder for creating and managing professional forms. It's perfect for collecting data, automating workflows, and integrating form submissions with your favorite services.
- [Formsite](https://composio.dev/toolkits/formsite) - Formsite lets you build online forms and surveys with drag-and-drop simplicity. Capture, manage, and integrate form responses securely for streamlined workflows.
- [Graphhopper](https://composio.dev/toolkits/graphhopper) - GraphHopper is an enterprise-grade Directions API for routing, optimization, and geocoding across multiple vehicle types. It enables fast, reliable route planning and logistics automation for businesses.
- [La Growth Machine](https://composio.dev/toolkits/lagrowthmachine) - La Growth Machine automates multi-channel sales outreach and routine tasks for sales teams. Streamline your workflow and focus on closing more deals.
- [Leverly](https://composio.dev/toolkits/leverly) - Leverly is a workflow automation platform that connects and coordinates actions across your apps. It streamlines repetitive processes so your business runs smoother, faster, and with fewer manual steps.
- [Maintainx](https://composio.dev/toolkits/maintainx) - Maintainx is a cloud-based CMMS for centralizing maintenance data, communication, and workflows. It helps organizations streamline maintenance operations and improve team coordination.
- [Make](https://composio.dev/toolkits/make) - Make is an automation platform that connects your favorite apps and services. Build powerful, custom workflows without writing code.
- [Ntfy](https://composio.dev/toolkits/ntfy) - Ntfy is a notification service to send push messages to phones or desktops. Instantly deliver alerts and updates to users, devices, or teams.
- [Persona](https://composio.dev/toolkits/persona) - Persona offers identity infrastructure to automate user verification and compliance. It helps organizations securely verify users and reduce fraud risk.

## Frequently Asked Questions

### 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 Mastra AI?

Yes, you can. Mastra AI 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)
