mx-technologies-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/mx-technologies-automation --openclawMX 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
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active MX Technologies connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmx_technologies - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitmx_technologies - 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: "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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/mx-technologies-automation/SKILL.mdView on GitHub Overview
Automates MX Technologies operations through Composio's MX Technologies toolkit via Rube MCP. It emphasizes always discovering current tool schemas with RUBE_SEARCH_TOOLS to keep workflows resilient to updates. The setup guides you to establish and verify a live MX connection before executing any tasks.
How This Skill Works
The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch current tool schemas. Next, it verifies an active MX connection using RUBE_MANAGE_CONNECTIONS with the mx_technologies toolkit. Finally, it executes the chosen tools via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the session ID; remember to include memory even if empty.
When to Use It
- Automating MX Technologies operations end-to-end using the Composio MX toolkit via Rube MCP.
- When tool schemas may change and you must fetch the latest definitions before running workflows.
- When establishing or revalidating an MX connection and ensuring it remains ACTIVE prior to execution.
- When chaining multiple MX tasks in a single session to maximize throughput and reuse a session_id.
- When performing bulk or batch MX tasks, leveraging RUBE_MULTI_EXECUTE_TOOL and related bulk tools.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS to verify MX Technologies tool schemas are current.
- Step 3: Use RUBE_MANAGE_CONNECTIONS to connect mx_technologies, then run a simple RUBE_MULTI_EXECUTE_TOOL workflow.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing to ensure current tool schemas.
- Verify that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before tool execution.
- Use exact field names and types from the search results; avoid hardcoding slugs or args.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and avoid creating new sessions unnecessarily; handle pagination tokens if provided.
Example Use Cases
- Schedule a daily MX data extraction task, using discovered tools, and generate a summarized report.
- Connect to the mx_technologies toolkit, then execute a predefined sequence of updates across MX records in one session.
- Run a batch of MX tasks in a single workflow by discovering tools first and executing multiple tool slugs with a shared session_id.
- Automatically adapt to tool schema changes by fetching latest schemas via RUBE_SEARCH_TOOLS before each run.
- Process large tool sets by handling pagination tokens and continuing to fetch until all tools have been executed.
