Do I need API keys to use Rube MCP?

No API keys are needed—just add the MCP endpoint (e.g., https://rube.app/mcp) as the MCP server.

Why must I search tools before executing?

Tool schemas change over time. RUBE_SEARCH_TOOLS fetches current slugs and input fields to prevent errors.

What about the memory parameter in executions?

Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is an empty object.

u301-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

U301 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/u301

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate U301 operations through Composio's U301 toolkit via Rube MCP. Always search for current tool schemas before executing workflows to ensure compatibility.

How This Skill Works

Connect to Rube MCP by adding the MCP endpoint, verify RUBE_SEARCH_TOOLS responds, and manage the U301 connection with RUBE_MANAGE_CONNECTIONS. Then discover tools with RUBE_SEARCH_TOOLS, select a tool slug and prepare exact argument fields from the schema, and execute via RUBE_MULTI_EXECUTE_TOOL, including a memory field and the active session.

When to Use It

Before starting a U301 workflow, run RUBE_SEARCH_TOOLS to fetch current tool schemas and available slugs.
When establishing or reconfirming a U301 connection, verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution.
During a multi-tool U301 workflow, use RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and exact argument fields.
If tool schemas change, re-run tool discovery instead of hardcoding slugs or args.
For multi-step tasks, reuse session IDs within a workflow and handle pagination tokens from tool discovery.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and ensure it is reachable.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current U301 tool slugs and input schemas.
Step 3: Connect to the U301 toolkit with RUBE_MANAGE_CONNECTIONS and then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and correct arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool
Verify the U301 connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
Use exact field names and types from the tool discovery results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and avoid unnecessary new sessions

Example Use Cases

Automate a U301 inventory update by discovering the relevant tool, validating its input schema, and executing with the proper memory payload.
Run a batch U301 operation that requires multiple tools in sequence within the same session.
Validate tool availability after a reset by re-running RUBE_SEARCH_TOOLS before execution.
Handle pagination in tool discovery to ensure all available tools are considered.
Troubleshoot by checking ACTIVE status via RUBE_MANAGE_CONNECTIONS before running any tool.

Frequently Asked Questions

Add this skill to your agents