How to integrate Anchor browser MCP with Claude Code

Manage your Anchor browser directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

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

Manage your Anchor browser directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Anchor browser with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Anchor browser to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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.

Connecting Anchor browser via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Anchor browser) for even more tool search precision. It's secure and reliable.

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, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Anchor browser account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['anchor_browser'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http anchor_browser-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Anchor browser. This URL will be used to connect Claude Code to Anchor browser.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Anchor browser
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Anchor browser MCP to Claude Code

bash
claude mcp add --transport http anchor_browser-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (anchor_browser-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Anchor browser MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your anchor_browser-composio entry in the list
  • This confirms that Claude Code can now access Anchor browser tools

If everything is wired up, you should see your anchor_browser-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Anchor browser

The first time you try to use Anchor browser tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Anchor browser
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Anchor browser authorization flow
  • Return to the terminal and start using Anchor browser through Claude Code

Once authenticated, you can ask Claude Code to perform Anchor browser operations in natural language. For example:

  • "Fetch full content of a product page"
  • "List all active browser sessions now"
  • "Get details for a specific browser profile"

Complete Code

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

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['anchor_browser'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http anchor_browser-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Anchor browser with Claude Code using Composio's MCP server. Now you can interact with Anchor browser directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Anchor browser operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Anchor browser operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

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.

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. Claude Code 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
Anchor browser MCP Integration with Claude Code | Composio