home / skills / composiohq / awesome-claude-skills / mapulus-automation

mapulus-automation skill

/mapulus-automation

This skill automates Mapulus tasks via Rube MCP by discovering current tool schemas first to ensure accurate, up-to-date workflow execution.

npx playbooks add skill composiohq/awesome-claude-skills --skill mapulus-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: mapulus-automation
description: "Automate Mapulus tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Mapulus Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/mapulus](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `mapulus`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates Mapulus tasks using Composio's Mapulus toolkit via Rube MCP. It provides a clear pattern to discover tools, verify connections, and execute Mapulus operations reliably. The workflow enforces schema discovery and connection checks to avoid runtime errors.

How this skill works

Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs, input schemas, recommended execution plans, and pagination tokens. Use RUBE_MANAGE_CONNECTIONS to ensure the Mapulus toolkit connection is active. Execute actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object) or run bulk jobs via RUBE_REMOTE_WORKBENCH using run_composio_tool().

When to use it

Automating Mapulus API workflows in an agent or orchestration pipeline.
Running bulk Mapulus operations that require discovered tool schemas.
Embedding Mapulus tasks in larger Composio/Rube MCP workflows.
When tool schemas or slugs may change frequently and must be discovered at runtime.
When you need robust connection checks and session reuse across multi-step flows.

Best practices

Always call RUBE_SEARCH_TOOLS first; do not hardcode tool slugs or argument shapes.
Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE for the mapulus toolkit before running tools.
Include a memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session_id for related workflows; generate a new session for distinct runs.
Respect exact field names and types returned by tool schemas to avoid validation errors.
Handle pagination tokens in search responses and continue fetching until complete.

Example use cases

Discover available Mapulus endpoints and run a data ingestion tool with schema-compliant args.
Batch-update Mapulus records using RUBE_REMOTE_WORKBENCH to parallelize run_composio_tool() jobs.
Automate an authorization flow by checking RUBE_MANAGE_CONNECTIONS and following returned auth links if not ACTIVE.
Compose multi-step workflows that query, transform, and push Mapulus data while reusing a session_id.
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS when complex validation or UI generation is needed.

FAQ

What must I call first before executing any Mapulus tool?

Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs and input schemas.

Do I need API keys to connect to Rube MCP?

No API keys are required; add the MCP server endpoint (https://rube.app/mcp) to your client configuration.

What if the connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then confirm ACTIVE before proceeding.