home / skills / composiohq / awesome-claude-skills / mx-technologies-automation

mx-technologies-automation skill

safe

/mx-technologies-automation

This skill automates MX Technologies tasks via Rube MCP, always discovering current tool schemas before execution to ensure accurate workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill mx-technologies-automation

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

Files (1)

SKILL.md

3.0 KB

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

# MX Technologies Automation via Rube MCP

Automate MX Technologies operations through Composio's MX Technologies toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/mx_technologies](https://composio.dev/toolkits/mx_technologies)

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["mx_technologies"]
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 MX Technologies-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `mx_technologies` |
| 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 MX Technologies tasks using Composio's MX Technologies toolkit via the Rube MCP gateway. It standardizes discovery, connection management, and execution patterns so workflows remain resilient to changing tool schemas. Follow the search-first pattern to retrieve current tool schemas before any execution.

How this skill works

The skill queries RUBE_SEARCH_TOOLS to discover available tool slugs, input schemas, recommended execution plans, and pagination tokens. It verifies or establishes an active MX Technologies connection using RUBE_MANAGE_CONNECTIONS, then runs one or more tools via RUBE_MULTI_EXECUTE_TOOL or bulk runs via RUBE_REMOTE_WORKBENCH. Calls always include session management and a memory object, and the skill enforces schema compliance and session reuse rules.

When to use it

Automate MX Technologies operations (data syncs, account actions, or reporting) via Composio/Rube MCP.
Build resilient agent workflows that must adapt to changing tool schemas and versions.
Execute bulk or multi-step MX workflows that require session and connection stability.
Run scheduled or on-demand automation without embedding static tool slugs or argument shapes.

Best practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and exact input schemas; never hardcode fields.
Confirm RUBE_MANAGE_CONNECTIONS returns ACTIVE for toolkit "mx_technologies" before executing tools.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs for related workflow steps; generate new session IDs for separate workflows.
Handle pagination tokens returned by search responses and fetch until complete.
Validate all arguments against the schema returned by RUBE_SEARCH_TOOLS to avoid runtime errors.

Example use cases

Discover and invoke an MX data export tool: search for export tool, validate schema, run RUBE_MULTI_EXECUTE_TOOL with correct args and memory.
Onboard a new MX connection: call RUBE_MANAGE_CONNECTIONS, follow returned auth link if not ACTIVE, then confirm status before running setup steps.
Bulk update accounts via RUBE_REMOTE_WORKBENCH: search for bulk-edit tool, craft run_composio_tool() payloads, and execute with session control.
Scheduled reporting: discover reporting tool schema, run multi-step queries across pages, and persist results using the memory parameter.

FAQ

Why must I call RUBE_SEARCH_TOOLS every time?

Tool schemas and available tool slugs can change. Searching first ensures you use the current schema and avoid mismatched arguments.

What happens if connection is not ACTIVE?

RUBE_MANAGE_CONNECTIONS returns an auth link or instructions; follow them to complete setup and then confirm ACTIVE status before running tools.

Is memory required for executions?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}), to comply with the execution protocol.