mx-toolbox-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/mx-toolbox-automation --openclawFiles (1)
SKILL.md
2.9 KB
Mx Toolbox Automation via Rube MCP
Automate Mx Toolbox operations through Composio's Mx Toolbox toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/mx_toolbox
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Mx Toolbox connection via
RUBE_MANAGE_CONNECTIONSwith toolkitmx_toolbox - 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_toolbox - 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 Toolbox 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 Toolbox task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["mx_toolbox"]
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 Toolbox-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit mx_toolbox |
| 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-toolbox-automation/SKILL.mdView on GitHub Overview
Automate Mx Toolbox operations through Composio's Mx Toolbox toolkit via Rube MCP. This skill guides you through discovery, connection, and execution using live tool schemas to keep workflows current.
How This Skill Works
The workflow discovers available Mx Toolbox tools with RUBE_SEARCH_TOOLS, then verifies and activates the mx_toolbox connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes tools through RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, always including memory and a session_id for continuity.
When to Use It
- You need to run a Mx Toolbox task without hardcoding tool slugs or arguments and want current schemas.
- Tool schemas may change and you must fetch fresh slugs and input fields before each run.
- You must confirm the Mx Toolbox connection is ACTIVE before executing any workflow.
- You want to perform a sequence of actions (discover -> connect -> execute) in a single automated workflow.
- You are performing bulk or repeated Mx Toolbox operations and want to reuse a session within the workflow.
Quick Start
- Step 1: Add Rube MCP endpoint (e.g., https://rube.app/mcp) as an MCP server in your client.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current Mx Toolbox tool slugs and schemas, then set up the mx_toolbox connection with RUBE_MANAGE_CONNECTIONS.
- Step 3: Execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug, including memory: {} and a session_id from your workflow.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas and slugs.
- Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow to maintain context; generate new ones for new workflows.
Example Use Cases
- Automate a daily MX record health check by discovering the relevant Mx Toolbox tool, establishing an active connection, and running the tool with a stored session.
- Batch-verify SPF and DKIM configurations across a list of domains by discovering tools, then executing them in a single session.
- Bulk blacklist status checks for multiple domains using RUBE_MULTI_EXECUTE_TOOL with a shared session and memory payload.
- Create a compliance report by chaining discovery, connection validation, and execution steps to collect results across tools.
- Onboard automation: connect to mx_toolbox, perform initial tool discovery, and run an initial health scan in one managed workflow.
Frequently Asked Questions
Add this skill to your agents
