How to integrate Browserbase tool MCP with LlamaIndex

Connect LlamaIndex to Browserbase tool MCP. Start a new headless browser session now, download all artifacts from last session, and more using natural language, with authentication handled for you.

Browserbase tool logoBrowserbase tool
Api Key

Browserbase is a serverless platform for running and managing headless browsers at scale. It lets you automate and monitor browser tasks with Playwright, Puppeteer, and Selenium—no infrastructure headaches.

64 Tools

Introduction

This guide walks you through connecting Browserbase tool to LlamaIndex using the Composio tool router. By the end, you'll have a working Browserbase tool agent that can create and manage browser sessions, run Browserbase agents, invoke functions, fetch pages, and download session replays and logs through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Browserbase tool account through Composio's Browserbase tool MCP server.

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

For exact tool slugs and parameter tables, see the tool catalog in the Composio docs.

Also integrate Browserbase tool with

TL;DR

Here's what you'll learn:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Browserbase tool
  • Connect LlamaIndex to the Browserbase tool MCP server
  • Build a Browserbase tool-powered agent using LlamaIndex
  • Interact with Browserbase tool through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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

The Browserbase MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Browserbase account. It provides structured and secure access to your browser sessions, contexts, projects, recordings, logs, files, and extensions, so your agent can create sessions, manage reusable contexts, inspect browser activity, retrieve recordings, and monitor project usage on your behalf.

  • Browser session management: Have your agent create isolated browser sessions, check their status, list recent sessions, and release running sessions when work is complete.
  • Reusable browser contexts: Let the agent create, inspect, and update browser contexts that preserve settings across multiple sessions.
  • Session monitoring and debugging: Direct your agent to retrieve live debugging access, review captured network activity, and inspect session logs.
  • Recordings and session artifacts: Instruct your agent to retrieve session replays, request downloadable recordings, and download generated session files.
  • Projects, files, and extensions: Have your agent review projects and usage, upload files for browser forms, and upload or inspect browser extensions.

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Browserbase tool account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Browserbase tool

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID
3

Installing dependencies

npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Browserbase tool access
5

Import modules

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

Create a new file called browserbase tool_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

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

What's happening:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

7

Create a Tool Router session and build the agent function

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["browserbase_tool"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Browserbase tool actions." ,
    llm,
    tools,
  });

  return agent;
}

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, browserbase tool)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Browserbase tool tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

What's happening:

  • We're creating a direct terminal interface to chat with Browserbase tool
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Browserbase tool tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Browserbase tool
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Browserbase tool, then start asking questions.

Complete Code

Here's the complete code to get you started with Browserbase tool and LlamaIndex:

import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

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

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["browserbase_tool"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Browserbase tool actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();

Conclusion

You've successfully connected Browserbase tool to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Browserbase tool tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.
TOOLS

Supported Tools

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

Attach Browserbase Function Secret

Attach an existing project secret to a Function by UUID.

Update Browser Context

Tool to update a specific browser context.

Create Browserbase Agent

Create a reusable browser agent with a name and optional system prompt and result schema.

Create Browser Context

Create a reusable browser context; the API key can select the project.

Create Browser Session

Create an isolated Browserbase session and return its connection details.

Create Browserbase Webhook

Register a publicly reachable HTTPS endpoint for project event deliveries.

Delete Browserbase Agent

Delete a reusable browser agent by its agentId.

Delete a browser context

Tool to delete a browser context and all its stored data (cookies, localStorage, etc.).

Delete Download

Delete a download file from storage and mark it as deleted.

Delete a browser extension

Tool to delete an uploaded browser extension by its ID.

Delete Session Downloads

Tool to delete all file downloads from a specific browser session.

Delete Browserbase Webhook

Delete a webhook, immediately stopping deliveries and retiring its secret.

Detach Browserbase Function Secret

Detach a project secret from a Function by UUID.

Download Session Artifacts

Download a completed session's generated files as a ZIP archive.

Fetch Browserbase Page

Fetch a page and return its content, headers, and metadata.

Get Browserbase Agent

Retrieve a reusable browser agent by its agentId.

Get Certificate

Retrieve a Browserbase certificate by its ID.

Get Browser Context

Return metadata for a browser context by ID.

Get Download

Get a single download by ID as metadata or a downloadable file object.

Retrieve a browser extension

Tool to retrieve details of a specific browser extension.

Get Browserbase Function

Retrieve a Browserbase function by its ID.

Get Browserbase Function Build

Retrieve a Browserbase function build by its build ID.

Get Browserbase Function Build Logs

Retrieve Browserbase function build logs by the build ID.

Get Browserbase Function Version

Retrieve a Browserbase function version by its version ID.

Get Browserbase Invocation

Retrieve a Browserbase function invocation by its invocation ID.

Get Browserbase Invocation Logs

Retrieve Browserbase function invocation logs by the invocation ID.

Get Browserbase Keypair

Retrieve the project's public HPKE encryption key and keypair ID.

Get Browserbase Project

Return project metadata, default timeout, and assigned concurrency.

Get project usage statistics

Tool to retrieve usage statistics for a project including browser minutes and proxy bytes consumed.

Get Browserbase Agent Run

Retrieve a browser agent run's current status, result, and session details.

Get Browserbase Secret

Retrieve a project secret's ID and name by UUID, without its secret value.

Get Browser Session

Return status, connection details, and timestamps for a browser session.

Get Session Debug URLs

Return live debugger and WebSocket URLs for a running browser session.

Get Session Logs

Return network request and response events captured during a browser session.

Get Session Replay

Return HLS replay metadata and page playlist paths for a recorded session.

Get Session Replay Page

Return the HLS M3U8 playlist for one recorded replay page.

Get Browserbase Webhook

Retrieve a single webhook by ID, without its signing secret.

Invoke Browserbase Function

Invoke a deployed Browserbase function asynchronously.

List Browserbase Agents

List one page of reusable browser agents across your account.

List Certificates

List Browserbase certificates with their IDs, timestamps, and project IDs.

List Browserbase Downloads

List one page of download metadata for a required browser session.

List Browserbase Function Builds

List one page of Browserbase function builds, optionally filtered by status.

List Browserbase Functions

List one page of Browserbase functions and the total number available.

List Browserbase Function Secrets

List one page of secret IDs and names attached to a Browserbase function, optionally filtered by creation time.

List Browserbase Function Versions

List one page of versions for a Browserbase function by its UUID.

List Browserbase Projects

List projects with their default timeout and assigned concurrency.

List Recording Downloads

Poll per-page MP4 assembly after requesting recording downloads until every page is COMPLETED or FAILED.

List Browserbase Run Messages

List a page of a browser agent run's messages, oldest first, with assistant or tool roles and text or typed content parts.

List Browserbase Agent Runs

List a page of browser agent runs across your account.

List Browserbase Secrets

List one page of project secret IDs and names, optionally filtered by creation time.

List Browser Sessions

List browser sessions, optionally filtered by status or user metadata.

List Browserbase Function Version Invocations

List one page of invocations for a Browserbase function version by its UUID.

List Browserbase Webhooks

List one page of the project's webhooks, newest first, without signing secrets.

Release Browser Session

Irreversibly request release of a running browser session, ending it before its configured timeout to avoid further charges.

Request Recording Downloads

Start asynchronous MP4 assembly for every recorded page of a completed session, then poll List Recording Downloads until every page is COMPLETED or FAILED.

Resume Browserbase Agent Run

Resume only a PAUSED browser agent run with optional additional input.

Run Browserbase Agent

Start a browser agent run to complete a task using web search and browser tools.

Stop Browserbase Agent Run

Request that an in-progress browser agent run stop.

Update Browserbase Agent

Update a reusable browser agent's name, system prompt, or result schema.

Update Browserbase Webhook

Update a webhook's delivery URL, subscribed event types, or both.

Upload Browser Extension

Tool to upload a browser extension for use in sessions.

Upload Session File

Upload one file so browser interactions can select it in a file input field.

Upload Session Files

Upload multiple files to one browser session for file-input interactions.

Web Search

Perform a web search and return structured results.

FAQ

Frequently asked questions

Start with Browserbase tool.It takes 30 seconds.

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

Start building