isaWOW
    Back to Skills & MCP Library
    Claude Skill · Productivity

    Browserhub Automation

    Automate Browserhub tasks via Rube MCP (Composio). Always search tools first for current schemas.

    Claude
    Claude Code
    OpenClaw
    Hermes
    View source

    Skill definition (SKILL.md)


    name: browserhub-automation description: "Automate Browserhub tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube]

    Browserhub Automation via Rube MCP

    Automate Browserhub operations through Composio's Browserhub toolkit via Rube MCP.

    Toolkit docs: composio.dev/toolkits/browserhub

    Prerequisites

    • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
    • Active Browserhub connection via RUBE_MANAGE_CONNECTIONS with toolkit browserhub
    • 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 browserhub
    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: "Browserhub 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 Browserhub task"}]
    session: {id: "existing_session_id"}
    

    Step 2: Check Connection

    RUBE_MANAGE_CONNECTIONS
    toolkits: ["browserhub"]
    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 Browserhub-specific use case
    ConnectRUBE_MANAGE_CONNECTIONS with toolkit browserhub
    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

    isaWOW · Custom Skill Development

    Want a custom Skill built for your team?

    We design private Claude, OpenClaw and Hermes Skills tailored to your workflows, SOPs and brand voice — production-ready in days.

    Get a custom Skill