Anchor Browser Automation via Rube MCP

SkillWeb & browsing

Your AI can handle browser tasks for you, like filling out forms and scraping pages, by working through Anchor Browser. Once this skill is added, it can automate those web tasks on your behalf. It searches the available actions first so it always works with up-to-date details.

Available today. Use it from your connected AI after setup.

After adding it, ask your AI to search the available browser actions to see what it can do. Then describe the task you want handled, such as filling a form or scraping a page.

Then ask your AI: use the Anchor Browser Automation via Rube MCP skill

What your AI can do with it

  • Fill out forms on websites
  • Scrape content from web pages
  • Automate browser tasks through Anchor Browser
  • Search available actions first to get up-to-date details

What this skill tells your AI

The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/anchor-browser-automation/SKILL.md and read by ahel’s review.

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.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit anchor_browser
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Anchor Browser-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit anchor_browser
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Signals

GitHub stars
16k
Forks
2k
Last commit
Jul 2026
Advanced
Catalog kind
skill
Gateway key
anchor-browser-automation
Source
github.com/composio-community/awesome-codex-skills