What is Rube MCP and how do I use it?

Rube MCP is the Composio middleware for managing tool integrations. Add https://rube.app/mcp as an MCP server and use RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL to automate Leadoku tasks.

Do I need to call RUBE_SEARCH_TOOLS every time?

Yes. Tool schemas can change, so always discover current tools and schemas before executing any Leadoku task.

What if tool schemas change after I start a workflow?

Retry discovery with RUBE_SEARCH_TOOLS to refresh slugs and input fields, then adjust your arguments accordingly before continuing.

leadoku-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Leadoku Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/leadoku

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Leadoku operations through Composio's Leadoku toolkit via Rube MCP. Always search for current tool schemas before running workflows to adapt to changes.

How This Skill Works

Discover available Leadoku tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify an ACTIVE Leadoku connection using RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session_id.

When to Use It

When starting a new Leadoku workflow and tool schemas may have changed, so you fetch current slugs and fields first.
When automating a recurring Leadoku operation (batch tasks) to ensure consistent tool usage each run.
When integrating Leadoku workflows into larger automation that requires session reuse across steps.
When validating that the Leadoku connection is ACTIVE before executing any tool.
When handling multi-page tool discoveries and needing to paginate through results to plan a run.

Quick Start

Step 1: Add Rube MCP as an MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Discover Leadoku tools with RUBE_SEARCH_TOOLS using use_case: 'Leadoku operations' to obtain tool slugs and schemas.
Step 3: Check connection with RUBE_MANAGE_CONNECTIONS for toolkits: ['leadoku'], then run RUBE_MULTI_EXECUTE_TOOL with the chosen slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get the latest tool schemas and slugs.
Check RUBE_MANAGE_CONNECTIONS status and ensure ACTIVE before execution.
Use exact field names and types from the search results to build arguments.
Include a memory parameter in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({ }).
Reuse session IDs within a workflow and fetch new ones only for new workflows.

Example Use Cases

Create a Leadoku task from a CRM event by discovering the appropriate tool slug and executing it with the required arguments.
Run a nightly batch to update multiple Leadoku tasks using the latest tool schemas.
Perform a scheduled Leadoku operation after confirming the Leadoku connection is ACTIVE.
Traverse paginated tool discovery results to assemble a comprehensive run plan for a complex workflow.
Execute several Leadoku tools in sequence using a single session_id to minimize latency.

Frequently Asked Questions

Add this skill to your agents