Anchor browser with Claude Agent SDK

How to integrate Anchor browser MCP with Claude Agent SDK

Trusted by

GET STARTED FOR FREE GET A DEMO

30 min · no commitment · see it on your stack

Introduction Also integrate Anchor browser with TL;DR What is Claude Agent SDK What is the Anchor browser MCP server Supported Tools & Triggers Creating MCP Server - Stand-alone vs Composio SDK Step-by-step Guide Complete Code Conclusion How to build Anchor browser MCP Agent with another framework Explore Other Toolkits FAQ

Connect Anchor browser without Auth hassles

We manage OAuth, API Key, token refresh, and scopes, you just build.

Try for Free

Introduction

This guide walks you through connecting Anchor browser to the Claude Agent SDK 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 Claude Agent SDK 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 SDK Claude Code Claude Cowork Codex OpenClaw Hermes CLI Google ADK LangChain Vercel AI SDK Mastra AI LlamaIndex CrewAI

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Anchor browser
Configure an AI agent that can use Anchor browser as a tool
Run a live chat session where you can ask the agent to perform Anchor browser operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

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.

Supported Tools & Triggers

Tools

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

Copy Selected TextTool to copy currently selected text in a browser session to the clipboard.

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

Create or Update Task DraftTool to create or update the draft version of a task.

Create ProfileCreates a new browser profile from an active session.

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

Delete ExtensionTool to delete a browser extension and remove it from storage.

Delete IntegrationTool to delete an existing integration and remove its stored credentials.

Delete ProfileTool to delete a browser profile by ID.

Delete TaskTool to soft delete a task and all its versions.

Delete Task VersionTool to soft delete a specific version of a task.

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

Double Click MouseTool to perform a double click at specified coordinates in a browser session.

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

End All SessionsTool to terminate all active browser sessions at once.

End Browser SessionTool to end a specific browser session by ID.

Get Batch Session StatusTool to retrieve detailed status information for a specific batch including progress and errors.

Get Browser SessionTool to retrieve detailed information about a specific browser session.

Get Clipboard ContentTool to retrieve the current content of the clipboard from a browser session.

Get Latest Task VersionTool 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 PagesTool to retrieve all pages associated with a specific browser session.

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

Get Task Execution ResultTool to retrieve a single task execution result by its ID.

Get Task MetadataTool to retrieve task metadata without downloading the full task code.

Get Task VersionTool to retrieve a specific version of a task, including the full code content.

Get Webpage ContentTool to retrieve rendered content of a webpage in HTML or Markdown format.

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

List ExtensionsRetrieves all browser extensions uploaded by the authenticated user.

List IntegrationsTool to retrieve all integrations for the authenticated team.

List ProfilesTool to fetch all stored browser profiles.

List Session DownloadsTool to retrieve metadata of files downloaded during a browser session.

List Session RecordingsTool to list all recordings for a specific browser session.

List SessionsTool to list all browser sessions.

List Task ExecutionsTool to retrieve execution history for a specific task with filtering and pagination support.

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

List Task VersionsTool to retrieve all versions of a specific task, including draft and published versions.

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

Navigate to URLTool to navigate a browser session to a specified URL.

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

Pause AgentTool to pause the AI agent for a specific browser session.

Pause Session RecordingTool to pause the video recording for a specific browser session.

Perform Keyboard ShortcutTool to perform a keyboard shortcut using specified keys in a browser session.

Perform Web TaskTool to perform autonomous web tasks using AI agents.

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

Publish Task VersionTool to publish a specific version of a task.

Release Mouse ButtonTool to release a mouse button at specified coordinates within a browser session.

Resume AgentTool to resume the AI agent for a specific browser session.

Resume Session RecordingTool to resume video recording for a specific browser session.

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

Run Task by NameTool to execute a task by its name, always using the latest version.

Screenshot WebpageTool to take a screenshot of a specified webpage within a session.

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

Set Clipboard ContentTool to set the content of the clipboard in a browser session.

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

Start Browser SessionTool to start a new browser session with optional customizations.

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

Type TextTool to type specified text with optional delay between keystrokes.

Update ProfileUpdates an existing browser profile with data from an active session.

Update Task MetadataUpdates task metadata (name and description).

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

Upload FileTool to upload a file to a browser session as an agent resource.

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

Wait for EventBlocks execution until a specific named event is signaled or the timeout expires.

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:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Anchor browser account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
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.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

composio-anthropic provides Composio integration for Anthropic
claude-agent-sdk is the core agent framework
python-dotenv loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The load_dotenv() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Anchor browser functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Anchor browser
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["anchor_browser"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Anchor browser
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Anchor browser tools via Composio.",
    max_turns=10
)

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Anchor browser
max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()

What's happening:

The Claude SDK client is created using the async context manager pattern
The agent processes each query and streams the response back in real-time
The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

What's happening:

This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Anchor browser and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Anchor browser
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["anchor_browser"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Anchor browser tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

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

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Anchor browser through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Anchor browser MCP Agent with another framework

OpenAI Agents SDK

Use Anchor browser MCP with OpenAI Agents SDK

Claude Code

Use Anchor browser MCP with Claude Code

Claude Cowork

Use Anchor browser MCP with Claude Cowork

Codex

Use Anchor browser MCP with Codex

OpenClaw

Use Anchor browser MCP with OpenClaw

Hermes

Use Anchor browser MCP with Hermes

CLI

Use Anchor browser MCP with CLI

Google ADK

Use Anchor browser MCP with Google ADK

LangChain

Use Anchor browser MCP with LangChain

Vercel AI SDK

Use Anchor browser MCP with Vercel AI SDK

Mastra AI

Use Anchor browser MCP with Mastra AI

LlamaIndex

Use Anchor browser MCP with LlamaIndex

CrewAI

Use Anchor browser MCP with CrewAI

Explore Other Toolkits

Supabase

Oauth2Api Key

Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure.

Codeinterpreter

No Auth

Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms.

GitHub

Oauth2

GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place.

TOOLKIT MARKETPLACE

FAQ

What are the differences in Tool Router MCP and Anchor browser MCP?

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.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Anchor browser tools.

Can I manage the permissions and scopes for Anchor browser while using Tool Router?

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.

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 Anchor browser data and credentials are handled as safely as possible.

Used by agents from

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for free Get a demo↗

Harsha GaddipatiCo-founder, Slashy

Karan skipped his own birthday party to fix our critical issue. It was 10 pm and he diverted his Waymo to help us instead. This really sets the bar, shows you the commitment you need to have when users rely on your software.

Abhi AryaCo-founder, Opennote

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 has immensely helped in keeping new users on the platform.

Nirman DaveCEO, Zams

We chose Composio over Pipedream because it delivered depth where it mattered. It supported niche tools and tricky edge cases that other platforms simply ignored. Giving us confidence to scale without compromising.

Ryan YuFounder, Extra Thursday

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down in the complexities of managing agent auth would have been a death sentence for Extra Thursday.

Tomisin JenrolaFounder & CEO, SwarmZero

Before partnering with Composio, adding tool integrations was a slow, resource-intensive process. Each integration could take weeks or months of engineering time, and maintaining them meant constantly keeping up with API changes.

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

Harsha GaddipatiCo-founder, Slashy

Abhi AryaCo-founder, Opennote

Nirman DaveCEO, Zams

Ryan YuFounder, Extra Thursday

Tomisin JenrolaFounder & CEO, SwarmZero

Jerome LeclancheCo-Founder, Ingram Technologies

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.

How to integrate Anchor browser MCP with Claude Agent SDK

Table of Contents

Connect Anchor browser without Auth hassles

Introduction

Also integrate Anchor browser with

TL;DR

What is Claude Agent SDK?

What is the Anchor browser MCP server, and what's possible with it?

Supported Tools & Triggers

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

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

How to build Anchor browser MCP Agent with another framework

OpenAI Agents SDK

Claude Code

Claude Cowork

Codex

OpenClaw

Hermes

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Explore Other Toolkits

Supabase

Codeinterpreter

GitHub

FAQ

What are the differences in Tool Router MCP and Anchor browser MCP?

Can I use Tool Router MCP with Claude Agent SDK?

Can I manage the permissions and scopes for Anchor browser while using Tool Router?

How safe is my data with Composio Tool Router?

Used by agents from

Never worry about agent reliability