Anchor Browser Automation

What This Skill Does

This skill automates Anchor Browser operations using the Composio Anchor Browser toolkit through Rube MCP. It's designed for users who need to automate web browsing tasks, such as data extraction, form filling, and website interaction. The skill ensures tools are up-to-date and connections are active before executing workflows.

When to Use

• Automate data extraction from websites.
• Fill out web forms automatically.
• Simulate user interactions on websites.
• Schedule automated browsing tasks.
• Monitor website content for changes.
• Automate web testing procedures.

Key Features

• Uses Rube MCP to manage Anchor Browser toolkit.
• Requires active Anchor Browser connection.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Checks connection status before execution.
• Executes tools using RUBE_MULTI_EXECUTE_TOOL.
• Provides documentation link for the Anchor Browser toolkit.

Manual Installation

Anchor Browser Automation via Rube MCP

Automate Anchor Browser operations through Composio's Anchor Browser toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/anchor_browser

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Anchor Browser connection via RUBE_MANAGE_CONNECTIONS with toolkit anchor_browser Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit anchor_browser If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Anchor Browser operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Anchor Browser task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["anchor_browser"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Anchor Browser Automation via Rube MCP

Automate Anchor Browser operations through Composio's Anchor Browser toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/anchor_browser