What is Rube MCP in relation to Fireberry automation?

Rube MCP is the Composio MCP server used to orchestrate Fireberry tools. It requires discovering tool schemas with RUBE_SEARCH_TOOLS and maintaining an ACTIVE connection via RUBE_MANAGE_CONNECTIONS before executing tools.

Do I always need to search for tools before running a task?

Yes. Tool schemas change regularly; always fetch current tool slugs and input schemas with RUBE_SEARCH_TOOLS rather than hardcoding values.

How can I ensure my workflow is ready to run?

Check that RUBE_SEARCH_TOOLS has returned tool schemas, verify the Fireberry connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, and include a memory object in RUBE_MULTI_EXECUTE_TOOL calls.

fireberry-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Fireberry Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fireberry

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["fireberry"]
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 Fireberry-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `fireberry`
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/fireberry-automation/SKILL.mdView on GitHub

Overview

Automate Fireberry operations through Composio's Fireberry toolkit using Rube MCP. The workflow always starts with RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an ACTIVE Fireberry connection before executing any tasks.

How This Skill Works

First, discover available Fireberry tools and their input schemas with RUBE_SEARCH_TOOLS. Next, ensure the Fireberry toolkit connection is ACTIVE via RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory state and the session_id derived from the discovery step.

When to Use It

When you need to automate a Fireberry workflow and must use the latest tool schemas (do not hardcode tool slugs or arguments).
When establishing or verifying an ACTIVE Rube MCP connection for the Fireberry toolkit before running workflows.
When orchestrating multiple Fireberry tools in a single session, reusing the session_id across steps.
When a workflow requires handling dynamic schemas or pagination in tool responses.
When performing bulk or remote batch Fireberry actions using tools like RUBE_REMOTE_WORKBENCH or run_composio_tool.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Fireberry operations' to discover tools and schemas.
Step 2: RUBE_MANAGE_CONNECTIONS for toolkits: ['fireberry']; ensure status is ACTIVE.
Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, memory: {}, and session_id from Step 1.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs, input schemas, and execution plans.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status for the fireberry toolkit before any execution.
Use exact field names and types from the search results; avoid hardcoding slugs or arguments.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows; monitor for pagination tokens.

Example Use Cases

Discover available Fireberry tools with RUBE_SEARCH_TOOLS, then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL with the required arguments and a session_id.
Set up the Fireberry toolkit by connecting via RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before running any workflows.
Create a multi-step Fireberry workflow that reuses a single session_id across steps to maintain state.
Adapt to changed tool schemas by always re-running RUBE_SEARCH_TOOLS prior to execution to fetch updated input fields.
Perform a bulk Fireberry operation using RUBE_REMOTE_WORKBENCH and run_composio_tool for efficiency.

Frequently Asked Questions

Add this skill to your agents