How to integrate Browser tool MCP with Claude Agent SDK

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Browser tool logo
Claude Agent SDK logo
divider

Introduction

This guide walks you through connecting Browser tool to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Browser tool agent that can copy highlighted text from this webpage, drag and drop a file to upload section, fetch and summarize main page content through natural language commands.

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

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

Also integrate Browser tool with

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 Browser tool
  • Configure an AI agent that can use Browser tool as a tool
  • Run a live chat session where you can ask the agent to perform Browser tool 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 Browser tool MCP server, and what's possible with it?

The Browser tool MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to browser automation tools. It provides structured and secure access to browser actions, so your agent can fetch web content, perform clicks, automate keyboard shortcuts, move the mouse, and interact with on-page elements just like a real user.

  • Fetch and analyze webpage content: Let your agent retrieve the full HTML or clean text of any web page for data extraction, analysis, or decision-making.
  • Automated mouse and keyboard interactions: Instruct your agent to perform precise clicks, double clicks, drags, and keyboard shortcuts to navigate, select, or manipulate content on the page.
  • Clipboard and text extraction: Have the agent copy highlighted text, read clipboard contents, or transfer data between the browser and other tools for seamless workflows.
  • Drag-and-drop automation: Enable your agent to handle complex drag-and-drop actions, such as moving files or rearranging lists, to mimic advanced user interactions.
  • Fine-grained UI element control: Direct your agent to move the mouse, press and hold, or release buttons at exact coordinates to interact with dynamic or custom web interfaces.

Supported Tools & Triggers

Tools
Run Browser TaskRun an AI-powered browser automation task.
Download Task FileGet a download URL for a file generated by a task.
Get Session Live URLGet the live URL to watch a browser session in real-time.
Stop Browser TaskKill a browser task and its session.
Watch Browser TaskPoll a browser task to check progress and get results.

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

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Browser tool 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 Browser tool 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 Browser tool
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["browser_tool"]
    )

    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 Browser tool
  • 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 Browser tool 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 Browser tool
  • 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 Browser tool 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 Browser tool
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["browser_tool"]
    )

    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 Browser tool 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 Browser tool 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 Browser tool MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Browser tool MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Browser tool MCP with OpenAI Agents SDK

Claude Code logo

Claude Code

Use Browser tool MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Browser tool MCP with Claude Cowork

Codex logo

Codex

Use Browser tool MCP with Codex

Cursor logo

Cursor

Use Browser tool MCP with Cursor

OpenClaw logo

OpenClaw

Use Browser tool MCP with OpenClaw

Hermes logo

Hermes

Use Browser tool MCP with Hermes

CLI logo

CLI

Use Browser tool MCP with CLI

Google ADK logo

Google ADK

Use Browser tool MCP with Google ADK

LangChain logo

LangChain

Use Browser tool MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Browser tool MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Browser tool MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Browser tool MCP with LlamaIndex

CrewAI logo

CrewAI

Use Browser tool MCP with CrewAI

OpenCode logo

OpenCode

Use Browser tool MCP with OpenCode

VS Code logo

VS Code

Use Browser tool MCP with VS Code

FAQ

What are the differences in Tool Router MCP and Browser tool MCP?

With a standalone Browser tool MCP server, the agents and LLMs can only access a fixed set of Browser tool tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Browser tool 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 Browser tool tools.

Can I manage the permissions and scopes for Browser tool while using Tool Router?

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

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

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 freeGet a demo↗