Hyperbrowser Automation

What This Skill Does

This skill automates Hyperbrowser operations using Composio's Hyperbrowser toolkit via Rube MCP. It allows users to streamline workflows within Hyperbrowser by programmatically interacting with its features. This is useful for anyone who needs to automate repetitive tasks or integrate Hyperbrowser with other systems.

When to Use

Automate data extraction from websitesMonitor website changes and trigger alertsFill out web forms automaticallyScrape product information from e-commerce sitesAutomate social media postingRun automated website tests

Key Features

Uses Rube MCP for tool discovery and executionRequires an active Hyperbrowser connectionDiscovers available tools and their schemas dynamicallyProvides a core workflow pattern for tool executionEmphasizes the importance of schema complianceHandles connection management via RUBE_MANAGE_CONNECTIONS

Manual Installation

Hyperbrowser Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hyperbrowser

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["hyperbrowser"] 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

Hyperbrowser Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/hyperbrowser