hyperbrowser-automation

Hyperbrowser Automation Skills

Skill Overview

By integrating the Composio Hyperbrowser toolset through the Rube MCP integration, you can orchestrate browser task automation. It supports tool discovery, connection management, and batch execution.

Suitable Scenarios

Web Automation

Use cases where an AI agent needs to perform browser actions—such as data scraping, form filling, and page navigation. Use the Rube MCP to call the Hyperbrowser tools in a unified way.

Tool-Driven Browser Workflows

Ideal for users who need to dynamically discover tool schemas and execute complex browser tasks. Use RUBE_SEARCH_TOOLS to retrieve the latest tool definitions and avoid hard-coding outdated APIs.

MCP Ecosystem Integration

Developers who have built AI applications using MCP (Model Context Protocol) can directly add a Rube MCP endpoint (https://rube.app/mcp). No additional authentication is required to use Hyperbrowser functionality.

Core Features

Tool Discovery and Schema Retrieval

Use RUBE_SEARCH_TOOLS to dynamically query available Hyperbrowser tools and obtain the latest tool slug, input schema, and execution recommendations. This helps avoid call failures caused by API changes.

Connection Management

Use RUBE_MANAGE_CONNECTIONS to manage the Hyperbrowser connection status. It supports connection activation, status checks, and authentication flows to ensure the connection is ready before workflow execution.

Batch Tool Execution

Execute multiple Hyperbrowser operations within a single session using RUBE_MULTI_EXECUTE_TOOL. It supports session reuse and memory passing, making it suitable for multi-step automation tasks.

Common Questions

How do I add a Rube MCP server?

Add the server endpoint https://rube.app/mcp in your MCP client configuration. Rube MCP does not require an API key. After adding it, you can use it directly. Once configured, call RUBE_SEARCH_TOOLS to verify that the connection is working properly.

Why call RUBE_SEARCH_TOOLS before executing a tool?

Hyperbrowser tool schemas change dynamically. Hard-coding tool slugs or parameters can easily lead to execution failures. RUBE_SEARCH_TOOLS returns the currently available tool definitions, input schemas, and known pitfalls to ensure you use the correct parameter structure during execution.

Does Rube MCP require an API key?

No. Rube MCP is a free service. Just add the endpoint https://rube.app/mcp in your MCP configuration to use it. However, Hyperbrowser itself may require authorization via RUBE_MANAGE_CONNECTIONS.

How can I reuse a Hyperbrowser session?

Use the session parameter in RUBE_SEARCH_TOOLS or RUBE_MULTI_EXECUTE_TOOL to pass an existing session_id. Operations within the same session can share state. For new workflows, it’s recommended to generate a new session ID.

What is the memory parameter in RUBE_MULTI_EXECUTE_TOOL for?

The memory parameter is used to pass and store contextual information during tool execution. Even if you don’t need to pass data right now, you must still include this parameter (set it to an empty object {}). This is a requirement of Rube MCP.