How to integrate Anchor browser MCP with LangChain

This guide walks you through connecting Anchor browser to LangChain 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 LangChain 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 LangChain 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 LangChain 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 ADKVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Anchor browser project to Composio
  • Create a Tool Router MCP session for Anchor browser
  • Initialize an MCP client and retrieve Anchor browser tools
  • Build a LangChain agent that can interact with Anchor browser
  • 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 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 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 Anchor browser 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 Anchor browser 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: ['anchor_browser']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Anchor browser 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 Anchor browser tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "anchor_browser-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 Anchor browser MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Anchor browser 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 Anchor browser 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 Anchor browser 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: ['anchor_browser']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "anchor_browser-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 Anchor browser 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 Anchor browser 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 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

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

LlamaIndex logo

LlamaIndex

Use Anchor browser MCP with LlamaIndex

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