anchor-browser-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/anchor-browser-automation --openclawAnchor 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_CONNECTIONSwith toolkitanchor_browser - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitanchor_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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Anchor Browser-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit anchor_browser |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/anchor-browser-automation/SKILL.mdView on GitHub Overview
Automate Anchor Browser operations using Composio's Anchor Browser toolkit via Rube MCP. The workflow relies on discovering current tool schemas first, establishing an ACTIVE anchor_browser connection, and then executing tools programmatically. This keeps automation resilient to changes and speeds up repetitive browser tasks.
How This Skill Works
Technically, you first discover available tools with RUBE_SEARCH_TOOLS to obtain current slugs and input schemas. Then you verify and manage the connection for the anchor_browser toolkit with RUBE_MANAGE_CONNECTIONS, ensuring the status is ACTIVE. Finally, you execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, a memory payload, and a session_id according to the schema.
When to Use It
- Automating recurring Anchor Browser tasks (data extraction, form submission, or routine navigations).
- Whenever tool schemas might change, so you always fetch current slugs and fields first.
- Building end-to-end browser workflows that reuse a session across steps.
- Running multiple tools in a single workflow with memory and a single session.
- Ensuring the anchor_browser connection is ACTIVE before deploying automation.
Quick Start
- Step 1: Add the Rube MCP endpoint and verify RUBE_SEARCH_TOOLS is responding.
- Step 2: Call RUBE_MANAGE_CONNECTIONS with the anchor_browser toolkit and confirm ACTIVE.
- Step 3: Discover tools and execute one with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results—don’t hardcode slugs or args.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow; generate new ones for new workflows.
Example Use Cases
- Discover tools for an Anchor Browser task, then run the matched tool to fetch page data.
- Create a reusable session and perform a sequence like navigation, data extraction, and save.
- Validate tool slugs with RUBE_SEARCH_TOOLS before upgrading an automation pipeline.
- Ensure the connection is ACTIVE and execute multiple tools in a single session.
- Bulk automate tasks using RUBE_REMOTE_WORKBENCH with run_composio_tool for efficiency.
