What is Rube MCP in this context?

Rube MCP is the Composio-based MCP server at rube.app that enables discovering tool schemas and managing connections for Kadoa automation.

Why do I have to search tools first?

Tool schemas change over time. Searching tools first ensures you use current slugs, input schemas, and execution plans instead of hardcoding values.

How do I ensure the tool schemas are up to date?

Always call RUBE_SEARCH_TOOLS to fetch current schemas and, if needed, use RUBE_GET_TOOL_SCHEMAS to review detailed field definitions before executing tools.

kadoa-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Kadoa Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/kadoa

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Kadoa operations through Composio's Kadoa toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to adapt to changes. This approach avoids hardcoding tool slugs and ensures reliable, schema-aligned automation.

How This Skill Works

Connect to Rube MCP and the Kadoa toolkit, then fetch current tool schemas with RUBE_SEARCH_TOOLS. Validate the connection with RUBE_MANAGE_CONNECTIONS and execute discovered tools using RUBE_MULTI_EXECUTE_TOOL, including a memory object and an active session. Tool schemas are retrieved live to keep automation aligned with available workflows.

When to Use It

Automating a Kadoa operation and needing the latest tool schemas before execution
Integrating Kadoa workflows into a batch automation or scheduled run
Preflight checks to ensure the Kadoa connection is ACTIVE before running tools
Reusing a session across multiple Kadoa steps in a single workflow
Handling changes in tool schemas or arguments without hardcoding slugs

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds and connect to the kadoa toolkit with RUBE_MANAGE_CONNECTIONS
Step 3: Discover tools using RUBE_SEARCH_TOOLS for your use case, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a memory object

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and avoid creating new ones for each step

Example Use Cases

Automate a Kadoa data sync by discovering tool slugs with RUBE_SEARCH_TOOLS and executing them in a single session
Orchestrate multiple Kadoa tasks in bulk by discovering several tools and running them via RUBE_MULTI_EXECUTE_TOOL
Run a preflight check to ensure the Kadoa connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before tasks
Implement schema-resilient automation by always fetching up to date tool schemas before execution
Execute a full Kadoa workflow with pagination handling by retrieving tools with RUBE_SEARCH_TOOLS and schemas with RUBE_GET_TOOL_SCHEMAS

Frequently Asked Questions

Add this skill to your agents