Browserbase Tool Automation

What This Skill Does

This skill automates Browserbase Tool operations via the Composio platform and Rube MCP. It facilitates programmatic interaction with Browserbase's features. It is useful for developers and automation engineers looking to integrate Browserbase into their automated workflows.

When to Use

• Automate tasks using Browserbase.
• Perform web scraping with Browserbase.
• Run browser tests using Browserbase.
• Manage Browserbase sessions.
• Simulate user actions with Browserbase.
• Integrate Browserbase into automation flows.

Key Features

• Utilizes Rube MCP for tool discovery.
• Requires an active Browserbase Tool connection.
• Provides a structured automation workflow.
• Emphasizes dynamic schema discovery.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

Browserbase Tool Automation via Rube MCP

Automate Browserbase Tool operations through Composio's Browserbase Tool toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/browserbase_tool

Prerequisites

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

Step 2: Check Connection

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