What is RUBE MCP and why is it required?

RUBE MCP is the central control plane for Composio tools. You add the MCP endpoint, verify availability with RUBE_SEARCH_TOOLS, and use it to manage Bart tool connections and executions.

Should I hardcode tool slugs?

No. Tool slugs can change as schemas update. Always fetch current tool slugs and input schemas with RUBE_SEARCH_TOOLS before executing.

How should memory and sessions be handled?

Always include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls and reuse session IDs within a workflow; generate new sessions only for new tasks.

bart-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Bart Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bart

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Bart operations through Composio's Bart toolkit using Rube MCP. Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and recommended execution plans. This ensures resilient, schema-compliant automation with an active Bart connection.

How This Skill Works

The skill connects to Rube MCP, discovers Bart tools, and checks the connection status. It then executes the chosen tool slug with the required arguments using RUBE_MULTI_EXECUTE_TOOL, ensuring memory is provided and the appropriate session_id is used. The workflow pattern follows discovery, connection check, and execution, with support for bulk operations when needed.

When to Use It

When you need to run a Bart operation with a runtime-defined tool slug discovered at runtime.
When tool schemas may change and you must fetch current inputs and slugs before automation.
When setting up a new Bart workflow and validating connectivity to the Bart toolkit.
When performing multi-tool executions or bulk operations via RUBE_REMOTE_WORKBENCH.
When reusing an existing workflow session to continue a Bart task without starting a new session.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and ensure RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkits: ["bart"] and verify the connection is ACTIVE.
Step 3: Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, including memory: {} and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any Bart workflow to fetch current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
Use exact field names and types from the tool schemas returned by the search.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}").
Reuse session IDs within a workflow and generate new ones only for new workflows.

Example Use Cases

Discover Bart tools with RUBE_SEARCH_TOOLS, connect to the bart toolkit, and execute a discovered tool_slug with the required arguments.
Connect to Bart via RUBE_MANAGE_CONNECTIONS and run a single Bart operation using RUBE_MULTI_EXECUTE_TOOL with proper memory and session_id.
Handle pagination in RUBE_SEARCH_TOOLS responses and fetch additional tool schemas until completion.
Maintain workflow continuity by reusing an existing session_id across multiple Bart tasks in a single run.
Perform bulk Bart actions using RUBE_REMOTE_WORKBENCH and run_composio_tool() for multiple tool executions in one session.

Frequently Asked Questions

Add this skill to your agents