What is required to start Cloudcart automation with Rube MCP?

RUBE MCP must be connected, RUBE_SEARCH_TOOLS must respond, and there must be an active Cloudcart connection via the cloudcart toolkit.

Should I always call RUBE_SEARCH_TOOLS before executing tools?

Yes. It fetches current tool slugs and input schemas to prevent schema drift.

Do I need to include a memory object in tool executions?

Yes. Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if it's an empty object.

cloudcart-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Cloudcart Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/cloudcart

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Cloudcart operations using Composio's Cloudcart toolkit through Rube MCP. This workflow emphasizes discovering tool schemas first, establishing an ACTIVE Cloudcart connection, and executing tools with schema-compliant arguments.

How This Skill Works

You first discover available Cloudcart tools with RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Next, you verify and establish a connection using RUBE_MANAGE_CONNECTIONS for the cloudcart toolkit, ensuring the status is ACTIVE. Finally, you execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the required arguments, a memory object, and a session_id for continuity.

When to Use It

When you need to discover current Cloudcart tool schemas before running any workflow
When establishing or revalidating a Cloudcart connection for automation
When executing a Cloudcart tool with schema-compliant arguments
When building multi-step Cloudcart workflows that require session reuse
When handling large results that may require pagination and multiple tool calls

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["cloudcart"] and ensure the status becomes ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to find a tool slug, then run RUBE_MULTI_EXECUTE_TOOL with memory and a valid session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to fetch up-to-date schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the cloudcart toolkit before running tools
Use exact field names and types from the search results; do not hardcode slugs or args
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs for related steps in a workflow and handle pagination tokens as needed

Example Use Cases

Discover the Cloudcart inventory_update tool with its input schema and run it to bulk update stock levels
Connect to Cloudcart via Rube MCP and run an order_sync tool to pull and process new orders
Fetch product_catalog, apply price_adjustments using the relevant tool, and save results with a shared session
Perform bulk product creation or updates by discovering the appropriate tool slug and supplying schema-compliant args
Navigate paginated results from a tool and continue fetching until all pages are processed in a single workflow

Frequently Asked Questions

Add this skill to your agents