What is RUBE MCP in this skill?

RUBE MCP is the Composio MCP server used to manage and orchestrate tools for Apipie AI via the apipie_ai toolkit.

Do I always need to search tools before running workflows?

Yes, to fetch current tool schemas and avoid hardcoding slugs.

What if the connection shows not ACTIVE?

Follow the included auth flow from the RUBE_MANAGE_CONNECTIONS response to activate it, then recheck.

apipie-ai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Apipie AI Automation via Rube MCP

Automate Apipie AI operations through Composio's Apipie AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/apipie_ai

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Apipie AI operations by leveraging Composio's Apipie AI toolkit through Rube MCP. It emphasizes discovering current tool schemas before execution and validating an active connection prior to running workflows.

How This Skill Works

First you ensure Rube MCP is connected and RUBE_SEARCH_TOOLS can fetch current tool schemas. Then you establish an ACTIVE apipie_ai connection with RUBE_MANAGE_CONNECTIONS, and finally execute the discovered tool slugs via RUBE_MULTI_EXECUTE_TOOL, supplying the exact input fields and including memory.

When to Use It

When you need to automate recurring Apipie AI tasks with up-to-date tool schemas
When you want to establish and verify a robust Rube MCP connection for the apipie_ai toolkit
When you must discover available tools before each workflow to avoid hard-coded slugs
When you need to execute discovered tools in a single session using RUBE_MULTI_EXECUTE_TOOL
When handling pagination and session reuse to maintain workflow continuity

Quick Start

Step 1: Add the Rube MCP endpoint and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to apipie_ai with RUBE_MANAGE_CONNECTIONS and complete auth if prompted
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the discovered schemas
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session_id within a workflow and avoid creating new sessions unnecessarily

Example Use Cases

Discover a tool slug from RUBE_SEARCH_TOOLS for an Apipie AI operation and run it with RUBE_MULTI_EXECUTE_TOOL using the returned schema
Connect to the apipie_ai toolkit via RUBE_MANAGE_CONNECTIONS and ensure status ACTIVE before execution
Run multiple tools in a single session by listing slugs in RUBE_MULTI_EXECUTE_TOOL and including memory
Handle pagination tokens from RUBE_SEARCH_TOOLS and continue fetching tool schemas until complete
Use RUBE_REMOTE_WORKBENCH with run_composio_tool for bulk operations on Apipie AI workflows

Frequently Asked Questions

Add this skill to your agents