kadoa-automation

Kadoa Automation - Rube MCP Automation Skills

Skill Overview

Automate Kadoa tasks using Composio’s Rube MCP service, providing a complete solution for tool discovery, connection management, and workflow execution.

Use Cases

1. Kadoa Workflow Automation

When you need to automatically execute Kadoa tasks, this skill dynamically discovers available tools, manages connection states, and batch-executes multiple actions—without manually calling APIs.

2. MCP Integration Development

While developing a Claude skill or an MCP client and integrating the Kadoa toolset, this skill offers an end-to-end integration pattern—from connection setup to standardized tool execution flow.

3. Batch Task Orchestration

When you need to run multiple Kadoa tool operations at the same time, or when orchestrating complex workflows in the Rube Remote Workbench, you can leverage the skill’s multi-tool execution capability and memory management features.

Core Features

Dynamic Tool Discovery

Use RUBE_SEARCH_TOOLS in real time to fetch the latest Kadoa tool schema, avoiding hard-coded tool slugs and parameters. This keeps you synchronized with updates from the Composio platform. Supports searching by use case, retrieving execution plans, and known pitfall prompts.

Connection Status Management

Use RUBE_MANAGE_CONNECTIONS to verify and activate Kadoa connections. Supports checking connection status, obtaining authorization links, and confirming activation status—ensuring connections are ready before tool execution.

Multi-Tool Batch Execution

Use RUBE_MULTI_EXECUTE_TOOL to call multiple Kadoa tools concurrently. Supports session reuse, memory management, and pagination, making it suitable for complex workflow scenarios. It also supports batch operations in RUBE_REMOTE_WORKBENCH using run_composio_tool().

Frequently Asked Questions

What is Rube MCP? Do I need an API key?

Rube MCP is Composio’s MCP server endpoint (https://rube.app/mcp) and does not require an API key. Add this endpoint to your MCP client configuration, and it will automatically provide tools such as RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS.

Why call RUBE_SEARCH_TOOLS first?

Kadoa tool schemas are updated frequently. Hard-coding tool slugs and parameters often leads to call failures. RUBE_SEARCH_TOOLS returns the latest tool definitions, input schemas, and recommended execution plans, including known pitfalls, to ensure successful calls.

How do I check whether a Kadoa connection is activated?

Call RUBE_MANAGE_CONNECTIONS with toolkits: ["kadoa"] and a session_id. If the returned connection status is not ACTIVE, you must complete the setup using the authorization link returned. Execute tool calls only after confirming activation.

Can multiple Kadoa tools be executed at the same time?

Yes. Use RUBE_MULTI_EXECUTE_TOOL and pass multiple tool objects in the tools array, each containing a tool_slug and schema-compliant arguments. Remember to include the memory parameter (even if it’s an empty object {}) and reuse the session_id.

What scenarios is RUBE_REMOTE_WORKBENCH for?

Use it when you need to orchestrate more complex batch operations in a remote workbench. You can call the run_composio_tool() function. This fits scenarios where you need to work with other Rube tools, or where the workflow requires conditional logic and loop handling.