Fireberry Automation

What This Skill Does

This skill automates Fireberry operations using the Composio Fireberry toolkit via Rube MCP. It enables users to streamline Fireberry tasks by discovering and executing tools through a standardized workflow. This skill is designed for users familiar with Fireberry and Rube MCP.

When to Use

• Automate data extraction.
• Manage Fireberry workflows.
• Generate reports.
• Check Fireberry connection status.
• Discover available Fireberry tools.
• Execute specific Fireberry tasks.

Key Features

• Uses Rube MCP to connect to Fireberry.
• Requires active Fireberry connection.
• Discovers available tools via RUBE_SEARCH_TOOLSChecks connection status with RUBE_MANAGE_CONNECTIONSExecutes tools with RUBE_MULTI_EXECUTE_TOOLProvides a standardized workflow for Fireberry automation.

Manual Installation

Manual installation

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

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

Toolkit docs: composio.dev/toolkits/fireberry