What is Rube MCP and how does it relate to Helcim automation?

Rube MCP provides a centralized interface to discover and execute Helcim tools via tool schemas. It ensures you use current tool definitions and manage connections safely before performing actions.

Do I always need to search tools first?

Yes. The SKILL emphasizes always calling RUBE_SEARCH_TOOLS first to retrieve up-to-date tool slugs, input schemas, and execution plans.

What if tool schemas change during a workflow?

Re-run RUBE_SEARCH_TOOLS to refresh schemas, then map inputs exactly to the updated fields. Ensure memory and session handling stay compliant with the latest schemas.

helcim-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Helcim Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/helcim

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Helcim operations through Composio's Helcim toolkit using Rube MCP. This skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflows. It guides setup, connection validation, tool discovery, and safe execution.

How This Skill Works

The workflow starts by discovering available Helcim tools with RUBE_SEARCH_TOOLS to pull current input schemas and recommended execution plans. It then validates the Helcim connection via RUBE_MANAGE_CONNECTIONS and executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a valid session_id. The process relies on exact schema field names/types from the search results and requires you to maintain connection and session state throughout the workflow.

When to Use It

When starting a Helcim workflow and needing current tool schemas
Before executing any tool to ensure the Helcim connection is ACTIVE
When exploring available Helcim tools for a specific task
When running multiple Helcim tools in a single session and reusing the session_id
When handling large results with pagination and updating tool schemas

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["helcim"] and confirm the status is ACTIVE
Step 3: Use RUBE_SEARCH_TOOLS to discover a Helcim tool, then execute it with RUBE_MULTI_EXECUTE_TOOL including a memory payload and a valid session_id

Best Practices

Always search for tool schemas first to avoid using stale or outdated tool slugs
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS
In every RUBE_MULTI_EXECUTE_TOOL call, include memory (even if empty) to satisfy the API
Reuse session IDs within a workflow and generate new ones for new workflows; handle pagination tokens as needed

Example Use Cases

Discover Helcim tools for a billing task with RUBE_SEARCH_TOOLS and execute the chosen TOOL_SLUG with the required inputs via RUBE_MULTI_EXECUTE_TOOL
Connect to the Helcim toolkit using RUBE_MANAGE_CONNECTIONS and verify ACTIVE before performing any operations
Update customer pricing in Helcim by locating the appropriate tool through RUBE_SEARCH_TOOLS and running it with schema-compliant arguments
Perform bulk Helcim operations in a single session, ensuring memory is provided in each RUBE_MULTI_EXECUTE_TOOL call
Fetch the full tool schemas for Helcim tools using RUBE_GET_TOOL_SCHEMAS and navigate pagination tokens to complete the fetch

Frequently Asked Questions

Add this skill to your agents