What is mboum-automation?

A workflow pattern that automates Mboum tasks via Rube MCP (Composio), always querying tool schemas first to stay in sync with live tool configurations.

What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, an active Mboum connection via RUBE_MANAGE_CONNECTIONS using the 'mboum' toolkit, and the ability to discover tool schemas before executing.

How do I discover and execute tools?

Use RUBE_SEARCH_TOOLS with the Mboum use case to discover tool slugs and input schemas, verify an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, then call RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and memory parameter.

mboum-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Mboum Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mboum

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Mboum operations through Composio's Mboum toolkit via Rube MCP. This approach fetches current tool schemas first, ensures an ACTIVE Mboum connection, and executes tools in structured steps, reducing manual overhead and errors.

How This Skill Works

The skill uses RUBE_SEARCH_TOOLS to fetch current Mboum tool schemas, then verifies an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the Mboum toolkit, and finally executes the selected tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, proper arguments, and a memory object. Workflows commonly follow Discover → Check Connection → Execute Tool, reusing sessions where appropriate.

When to Use It

Automating recurring Mboum tasks by composing tool workflows
When tool schemas change and you want to avoid hardcoding slugs or arguments
Before executing Mboum workflows to verify an ACTIVE connection
When discovering available Mboum tools and their input schemas
For batch or bulk Mboum operations using multiple tools

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Mboum tool schemas for your task
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit 'mboum' and then RUBE_MULTI_EXECUTE_TOOL with the chosen tool slug and arguments

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows
Use exact field names and types from the tool schemas
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new tasks

Example Use Cases

Discover Mboum tools for a specific task, connect the Mboum toolkit, and execute a tool with the discovered slug and args
Run a batch of Mboum operations in a single workflow using RUBE_MULTI_EXECUTE_TOOL with a shared session
Adapt to tool-schema changes by re-discovering tools instead of hardcoding slugs
Validate that the Mboum connection is ACTIVE before executing any tool
Use RUBE_REMOTE_WORKBENCH to run multiple tools in bulk via run_composio_tool()

Frequently Asked Questions

Add this skill to your agents