Anchor Browser Automation — Automate Browser Tasks via Rube MCP

Skill Overview

Automate Anchor Browser operations using Composio’s Rube MCP service, without writing code, to manage browser tasks and perform bulk operations.

Use Cases

1. Automating Repetitive Browser Tasks When you need to regularly perform the same browser actions, this skill can handle tasks in bulk via RUBE_MULTI_EXECUTE_TOOL, avoiding manual repetition.

2. Dynamic Tool Discovery and Integration If the tool architecture may change, use RUBE_SEARCH_TOOLS to always retrieve the latest tool schema, preventing integration failures caused by hardcoding.

3. Browser Operations Requiring MCP Connections If you want to interact with Anchor Browser through the standard MCP protocol rather than calling APIs directly, this skill provides complete connection management and workflow support.

Core Features

1. Intelligent Tool Discovery Use RUBE_SEARCH_TOOLS to fetch the latest Anchor Browser tool architecture in real time, returning available tool slugs, input parameters, and recommended execution plans—ensuring compatibility with APIs that are continuously updated.

2. Connection Status Management Use RUBE_MANAGE_CONNECTIONS to check and manage the Anchor Browser connection status. This ensures the connection is active before executing tasks, and supports quick configuration via an auth link.

3. Bulk Task Execution Use RUBE_MULTI_EXECUTE_TOOL to support bulk calls to multiple tools. Combined with RUBE_REMOTE_WORKBENCH, you can run complex workflows on a remote workbench, reducing session-switching overhead.

Frequently Asked Questions

What is Rube MCP? Is it paid or does it require an API key?

Rube MCP is a free MCP service endpoint provided by Composio. You only need to add https://rube.app/mcp to your client configuration—no API key or paid subscription is required. After connecting, you will automatically receive access permissions to multiple tool suites, including Anchor Browser.

Why call RUBE_SEARCH_TOOLS first?

The Anchor Browser tool architecture (including tool slugs, parameter names, and types) changes with version updates. Directly hardcoding tool calls is likely to break after a new version is released. RUBE_SEARCH_TOOLS returns the currently accurate tool schema and recommended execution plan, ensuring your automation workflows remain compatible with the latest API.

How to handle an Anchor Browser connection in a non-active state?

When using it for the first time or when the connection has expired, calling RUBE_MANAGE_CONNECTIONS returns the status and an authorization link. Click the returned auth link to authorize your Anchor Browser account, then call the check interface again to confirm the status becomes ACTIVE before you run tools normally. It’s recommended to verify connection status at the start of each workflow.