How to integrate Anchor browser MCP with OpenClaw

Framework Integration Gradient
Anchor browser Logo
OpenClaw Logo
divider

Introduction

OpenClaw is the fastest growing agent harness out there, which can work 24/7 to automate almost any kind of tasks. However, its capabilities are limited to the tools it has access to. Composio allows your OpenClaw to access Anchor browser with authentication management handled for you. You can execute actions on Anchor browser via your favorite OpenClaw interface (Telegram, WhatsApp, TUI, etc), whichever you prefer.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • 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 850+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

How to install Anchor browser with OpenClaw

Using Composio API Key and Setup Prompt

Copy the setup prompt from the OpenClaw dashboard
  • Run it in your OpenClaw chat interface.
  • Authenticate Anchor browser from the dashboard
  • Go back to your OpenClaw interface and start asking questions.

Using OpenClaw/Composio Plugin

1. Install OpenClaw Composio plugin

bash
openclaw plugins install @composio/openclaw-plugin

2. Copy the API Key from dashboard.composio.dev

3. Setup OpenClaw Config

openclaw config set plugins.entries.composio.config.consumerKey "ck_your_key_here"

4. Restart OpenClaw

openclaw gateway restart

5. Go to your chat interface and start asking questions.

6. When prompted, authenticate the app and you're all set.

How It Works

The plugin connects to Composio's MCP server at https://connect.composio.dev/mcp and registers all available tools directly into the OpenClaw agent. Tools are called by name — no extra search or execute steps needed.

If a tool returns an auth error, the agent will prompt you to connect that toolkit at dashboard.composio.dev.

Configuration

{
  "plugins": {
    "entries": {
      "composio": {
        "enabled": true,
        "config": {
          "consumerKey": "ck_your_key_here"
        }
      }
    }
  }
}
OptionDescriptionDefault
enabledEnable or disable the plugintrue
consumerKeyYour Composio consumer key (ck_...)
mcpUrlMCP server URL (advanced)https://connect.composio.dev/mcp

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
Create ProfileTool to create a new browser profile from an active session.
Delete ProfileTool to delete a browser profile by id.
End All SessionsTool to end all active browser sessions.
End Browser SessionTool to end a specific browser session by id.
Get ProfileTool to fetch details for a specific browser profile by id.
Get Webpage ContentTool to retrieve rendered content of a webpage in html or markdown format.
List Agent ResourcesTool to list agent resources (files) for a given session.
List All Sessions StatusTool to list the status of all active browser sessions.
List ExtensionsTool to list all browser extensions for the authenticated user.
List ProfilesTool to fetch all stored browser profiles.
List Session RecordingsTool to list all recordings for a specific browser session.
List SessionsTool to list all browser sessions.
Screenshot WebpageTool to take a screenshot of a specified webpage within a 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.
Update ProfileTool to update an existing browser profile by id.
Upload FileTool to upload a file to a browser session as an agent resource.
Wait for EventTool to wait for a specific event.

Conclusion

You've successfully integrated Anchor browser with OpenClaw using Composio plugin. Now interact with Anchor browser directly from your terminal, Web UI, or any messenger app using natural language commands.

Key benefits of this setup:

  • Seamless integration across TUI, Web UIs, and Messenger apps like Telegram, WhatsApp, Slack, etc.
  • Natural language commands for Anchor browser operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 850+ apps for cross-app workflows
  • Programmatic tool calling for complex tool chaining

Next steps:

  • Try asking OpenClaw to perform various Anchor browser operations
  • Explore cross-app workflows by connecting more toolkits like Calendar, Slack, Notion, etc.
  • Build complex automation scripts that leverage OpenClaw's 24/7 running capabilities

How to build Anchor browser MCP Agent with another framework

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 OpenClaw?

Yes, you can. OpenClaw 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

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.