Browserhub Automation

What This Skill Does

• This skill automates Browserhub operations through Composio's platform using Rube MCP.
• It allows users to programmatically interact with Browserhub's functionalities.
• It's designed for developers and automation engineers who need to integrate Browserhub into their automated processes.

When to Use

• Automate browser-based workflows.
• Perform web scraping tasks.
• Run automated browser tests.
• Manage browser sessions programmatically.
• Simulate user interactions on websites.
• Integrate browser actions into applications.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Browserhub connection.
• Provides a structured workflow for automation.
• Emphasizes the importance of dynamic schema discovery.
• Offers connection management via RUBE_MANAGE_CONNECTIONS.
• Executes tasks using RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed 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

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: {}

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