What is Rube MCP and Kit toolkit?

Rube MCP provides a centralized control plane; the Kit toolkit enables automating Kit operations via Composio.

Why must I search tools before running tasks?

Tool schemas change frequently; fetching current slugs ensures you use valid inputs and avoid failures.

What if the connection status isn't ACTIVE?

Follow the auth link from RUBE_MANAGE_CONNECTIONS to complete setup and then re-check ACTIVE before executing tools.

kit-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Kit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/kit

Prerequisites

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

Step 2: Check Connection

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

Overview

Kit Automation via Rube MCP lets you automate Kit operations through Composio's Kit toolkit. It requires querying tool schemas with RUBE_SEARCH_TOOLS, ensuring an active Kit connection via RUBE_MANAGE_CONNECTIONS, and then executing tools through RUBE_MULTI_EXECUTE_TOOL. This keeps workflows current with tool schemas and avoids hardcoding slugs.

How This Skill Works

First, discover available tools with RUBE_SEARCH_TOOLS to fetch current slugs and input schemas. Next, verify the Kit connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, sending the exact schema fields and a memory payload, and reuse session_id when appropriate.

When to Use It

Automating Kit operations via Composio toolkit
Tool schemas change frequently—fetch current slugs before running
Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Discover tools for a specific Kit task prior to workflow steps
Execute multi-step workflows using the discovered tool slugs with a memory payload

Quick Start

Step 1: Verify RUBE_SEARCH_TOOLS responds to confirm MCP availability
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit 'kit' and ensure status is ACTIVE
Step 3: Resolve TOOL_SLUG_FROM_SEARCH and run RUBE_MULTI_EXECUTE_TOOL with memory: {} and your session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution
Use exact field names and types from the search results
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs for related steps to maintain context

Example Use Cases

Discover Kit tools for 'inventory update', start a session, then run a discovered tool with proper arguments
Set up Rube MCP, verify ACTIVE connection, and automate a kit task end-to-end
For a multi-step workflow, fetch tool schemas, connect, and execute tools in sequence with memory
Always fetch current tool slugs before coding a kit automation script
Handle pagination tokens from RUBE_SEARCH_TOOLS responses and continue fetching until complete

Frequently Asked Questions

Add this skill to your agents