How to integrate Anchor browser MCP with LlamaIndex

This guide walks you through connecting Anchor browser to LlamaIndex using the Composio tool router. By the end, you'll have a working Anchor browser agent that can fetch full content of a product page, list all active browser sessions now, get details for a specific browser profile through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Anchor browser account through Composio's Anchor browser 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
Anchor browser logoAnchor browser
Api Key

Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction.

64 Tools

Introduction

This guide walks you through connecting Anchor browser to LlamaIndex using the Composio tool router. By the end, you'll have a working Anchor browser agent that can fetch full content of a product page, list all active browser sessions now, get details for a specific browser profile through natural language commands.

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

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

Also integrate Anchor browser with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AICrewAI

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 Anchor browser
  • Connect LlamaIndex to the Anchor browser MCP server
  • Build a Anchor browser-powered agent using LlamaIndex
  • Interact with Anchor browser 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 Anchor browser MCP server, and what's possible with it?

The Anchor browser MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Anchor browser account. It provides structured and secure access to powerful web automation features, so your agent can fetch web content, manage browser sessions, control profiles, and interact with extensions on your behalf.

  • Automated webpage content retrieval: Instruct your agent to browse to any URL and fetch the fully rendered page content in HTML or markdown, enabling easy scraping or summarization.
  • Session and profile management: Let your agent create, list, or delete browser profiles, as well as start, end, or monitor multiple browsing sessions for different workflows or user contexts.
  • Browser extension control: Have the agent list all installed browser extensions, making it easy to audit and manage your browser environment programmatically.
  • Resource and file listing: Ask your agent to retrieve a list of files or resources uploaded during browser automation tasks, ensuring nothing gets lost in the shuffle.
  • Comprehensive session oversight: Quickly get an overview of all active browser sessions, their statuses, and terminate any or all sessions instantly for security or resource management needs.

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 Anchor browser account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Anchor browser

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 Anchor browser 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 anchor browser_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: ["anchor_browser"],
    },
  );

  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 Anchor browser 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, anchor browser)
  • 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 Anchor browser 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 Anchor browser
  • 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 Anchor browser 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 Anchor browser
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Anchor browser, then start asking questions.

Complete Code

Here's the complete code to get you started with Anchor browser 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: ["anchor_browser"],
    },
  );

  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 Anchor browser 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 Anchor browser to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Anchor browser 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 Anchor browser action and event your agent gets out of the box.

Click Mouse

Tool to perform a mouse click at specified coordinates within a browser session.

Copy Selected Text

Tool to copy currently selected text in a browser session to the clipboard.

Create Integration

Tool to create a new integration with a third-party service like 1Password.

Create or Update Task Draft

Tool to create or update the draft version of a task.

Create Profile

Creates a new browser profile from an active session.

Create Task

Tool to create a new task or update an existing task with the same name.

Delete Extension

Tool to delete a browser extension and remove it from storage.

Delete Integration

Tool to delete an existing integration and remove its stored credentials.

Delete Profile

Tool to delete a browser profile by ID.

Delete Task

Tool to soft delete a task and all its versions.

Delete Task Version

Tool to soft delete a specific version of a task.

Deploy Task

Tool to deploy a task by creating a new version with auto-incremented version number.

Double Click Mouse

Tool to perform a double click at specified coordinates in a browser session.

Drag and Drop

Tool to perform a drag and drop operation from start coordinates to end coordinates within a browser session.

End All Sessions

Tool to terminate all active browser sessions at once.

End Browser Session

Tool to end a specific browser session by ID.

Get Batch Session Status

Tool to retrieve detailed status information for a specific batch including progress and errors.

Get Browser Session

Tool to retrieve detailed information about a specific browser session.

Get Clipboard Content

Tool to retrieve the current content of the clipboard from a browser session.

Get Latest Task Version

Tool to retrieve the latest version of a task including the full base64 encoded code content.

Get Profile (v2)

Tool to retrieve details of a specific profile by its name.

Get Session Pages

Tool to retrieve all pages associated with a specific browser session.

Get Task Draft

Tool to retrieve the draft version of a task, including the full Base64 encoded code content.

Get Task Execution Result

Tool to retrieve a single task execution result by its ID.

Get Task Metadata

Tool to retrieve task metadata without downloading the full task code.

Get Task Version

Tool to retrieve a specific version of a task, including the full code content.

Get Webpage Content

Tool to retrieve rendered content of a webpage in HTML or Markdown format.

List Agent Resources

List all agent resources (files) uploaded to a browser session.

List Extensions

Retrieves all browser extensions uploaded by the authenticated user.

List Integrations

Tool to retrieve all integrations for the authenticated team.

List Profiles

Tool to fetch all stored browser profiles.

List Session Downloads

Tool to retrieve metadata of files downloaded during a browser session.

List Session Recordings

Tool to list all recordings for a specific browser session.

List Sessions

Tool to list all browser sessions.

List Task Executions

Tool to retrieve execution history for a specific task with filtering and pagination support.

List Tasks

Tool to retrieve a paginated list of all tasks for the authenticated team.

List Task Versions

Tool to retrieve all versions of a specific task, including draft and published versions.

Mouse Move

Tool to move the mouse cursor to specified coordinates within a browser session.

Navigate to URL

Tool to navigate a browser session to a specified URL.

Paste Text

Tool to paste text at the current cursor position in a browser session.

Pause Agent

Tool to pause the AI agent for a specific browser session.

Pause Session Recording

Tool to pause the video recording for a specific browser session.

Perform Keyboard Shortcut

Tool to perform a keyboard shortcut using specified keys in a browser session.

Perform Web Task

Tool to perform autonomous web tasks using AI agents.

Mouse Down

Tool to perform a mouse button down action at specified coordinates within a browser session.

Publish Task Version

Tool to publish a specific version of a task.

Release Mouse Button

Tool to release a mouse button at specified coordinates within a browser session.

Resume Agent

Tool to resume the AI agent for a specific browser session.

Resume Session Recording

Tool to resume video recording for a specific browser session.

Run Task

Tool to execute a task in a browser session with a specific or latest version.

Run Task by Name

Tool to execute a task by its name, always using the latest version.

Screenshot Webpage

Tool to take a screenshot of a specified webpage within a session.

Scroll Session

Tool to perform a scroll action at specified coordinates within a browser session.

Set Clipboard Content

Tool to set the content of the clipboard in a browser session.

Signal Event

Tool to signal a specific event to be received by other processes or sessions.

Start Browser Session

Tool to start a new browser session with optional customizations.

Take Screenshot

Tool to take a screenshot of the current browser session and return it as an image.

Type Text

Tool to type specified text with optional delay between keystrokes.

Update Profile

Updates an existing browser profile with data from an active session.

Update Task Metadata

Updates task metadata (name and description).

Upload Extension

Tool to upload a new browser extension as a ZIP file for use in browser sessions.

Upload File

Tool to upload a file to a browser session as an agent resource.

Upload Files to Session

Tool to upload files directly to a browser session for use with web forms and file inputs.

Wait for Event

Blocks execution until a specific named event is signaled or the timeout expires.

FRAMEWORKS

How to build Anchor browser MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Anchor browser MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Anchor browser MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Anchor browser MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Anchor browser MCP with Claude Cowork

Codex logo

Codex

Use Anchor browser MCP with Codex

OpenClaw logo

OpenClaw

Use Anchor browser MCP with OpenClaw

Hermes logo

Hermes

Use Anchor browser MCP with Hermes

CLI logo

CLI

Use Anchor browser MCP with CLI

Google ADK logo

Google ADK

Use Anchor browser MCP with Google ADK

LangChain logo

LangChain

Use Anchor browser MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Anchor browser MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Anchor browser MCP with Mastra AI

CrewAI logo

CrewAI

Use Anchor browser MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Anchor browser MCP server, the agents and LLMs can only access a fixed set of Anchor browser tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Anchor browser and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LlamaIndex 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 Anchor browser tools.

Yes, absolutely. You can configure which Anchor browser 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 Anchor browser data and credentials are handled as safely as possible.

Start with Anchor browser.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Anchor browser 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