Do I need API keys to use mapulus-automation?

No API keys are needed; configure the MCP endpoint (https://rube.app/mcp) and ensure RUBE_SEARCH_TOOLS responds.

Why must I always call RUBE_SEARCH_TOOLS first?

Tool schemas change frequently. Fetch current slugs and input schemas to avoid failures.

How can I verify the Mapulus connection is ready?

Check RUBE_MANAGE_CONNECTIONS and ensure the toolkit mapulus shows ACTIVE before executing tools.

mapulus-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Mapulus Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mapulus

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Mapulus operations through Composio's Mapulus toolkit using Rube MCP. Always fetch current tool schemas with RUBE_SEARCH_TOOLS to adapt workflows as tool slugs and inputs change.

How This Skill Works

Connect to Rube MCP and ensure RUBE_SEARCH_TOOLS responds. Verify an ACTIVE Mapulus connection with RUBE_MANAGE_CONNECTIONS for the mapulus toolkit. Discover available tools, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, provided arguments, memory, and a session_id.

When to Use It

You are setting up a new Mapulus workflow and need the latest tool schemas
You have just established a Mapulus connection and want to start automation
You need to run a sequence of tools within a single session
Tool schemas have changed and you must fetch updated slugs and inputs
Batch processing requires fetching all tool options before execution, handling pagination if present

Quick Start

Step 1: Configure RUBE MCP by adding the MCP endpoint https://rube.app/mcp and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover Mapulus tools with RUBE_SEARCH_TOOLS for Mapulus use cases and capture tool slugs and input schemas
Step 3: Connect and execute: run RUBE_MANAGE_CONNECTIONS for toolkit mapulus, then RUBE_MULTI_EXECUTE_TOOL with a discovered slug, proper arguments, memory, and session_id

Best Practices

Always search first with RUBE_SEARCH_TOOLS before any execution
Verify the Mapulus connection is ACTIVE via RUBE_MANAGE_CONNECTIONS
Use exact field names and types from the discovered tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and handle pagination when responses are paginated

Example Use Cases

End-to-end Mapulus automation: discover tools, authenticate, and execute a chosen tool in a single workflow
Adapt to tool changes by re-running RUBE_SEARCH_TOOLS before executing any tool
Run a batch of Mapulus tasks within one session across multiple tools
If connection shows not ACTIVE, follow the provided auth flow and retry until ACTIVE
Inspect full tool schemas with RUBE_GET_TOOL_SCHEMAS to plan complex payloads

Frequently Asked Questions

Add this skill to your agents