What is Rube MCP and how does it relate to Browserhub automation?

Rube MCP is Composio's MCP server used to manage tool discovery, connections, and execution. This skill uses RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL to automate Browserhub tasks.

Do I need an API key to use this skill?

No API keys are needed — you simply add the MCP endpoint (e.g., https://rube.app/mcp) in your client configuration.

What should I do if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch current schemas before executing tools; avoid hardcoding tool slugs or argument structures.

browserhub-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/browserhub-automation --openclaw

Files (1)

SKILL.md

2.9 KB

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit browserhub
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: "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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Browserhub-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `browserhub`
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/browserhub-automation/SKILL.mdView on GitHub

Overview

This skill automates Browserhub operations by interfacing with Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first, establishing an active Browserhub connection, and executing tools through RUBE_MULTI_EXECUTE_TOOL. Using this approach keeps automations aligned with live Browserhub capabilities and avoids hardcoding slugs.

How This Skill Works

You first fetch available Browserhub tool schemas with RUBE_SEARCH_TOOLS, then verify an ACTIVE Browserhub connection via RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with a session_id and a memory payload. Prerequisites include a connected Rube MCP and an active Browserhub connection; always search for schemas before execution.

When to Use It

You need up-to-date Browserhub tool schemas before automating a task.
You must ensure the Browserhub connection is ACTIVE before running tools.
You want to reuse a session_id across multiple steps in a workflow.
Tool slugs or required arguments may change; avoid hardcoding values.
You are performing bulk or multi-tool operations and require orchestration.

Quick Start

Step 1: Get Rube MCP and verify connectivity: add https://rube.app/mcp as an MCP server, then run RUBE_SEARCH_TOOLS to confirm availability.
Step 2: Establish Browserhub connection: run RUBE_MANAGE_CONNECTIONS with toolkit 'browserhub' and ensure the status is ACTIVE.
Step 3: Discover and execute: use RUBE_SEARCH_TOOLS for your use_case, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to execution.
Use exact field names and types from the live tool schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow; generate new sessions only when needed.

Example Use Cases

Discover Browserhub tools for a login task and run the appropriate tool using the latest schema.
Connect to Browserhub and execute a data-export task with a discovered tool slug.
Reuse an existing session_id across multiple Browserhub steps in a single workflow.
Perform a bulk Browserhub operation via RUBE_REMOTE_WORKBENCH using run_composio_tool().
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to review required fields before automation.

Frequently Asked Questions

Add this skill to your agents