moxie-automation

Moxie Automation Skill - Simplify Composio Integration via Rube MCP

Skill Overview

The Moxie Automation Skill provides a standardized workflow through Rube MCP (Composio) to help you discover tools, manage connections, and execute Moxie actions—without having to directly handle complex API calls.

Use Cases

Automated Deployment of Moxie Projects: When you need to create, update, or manage Moxie projects in bulk, you can use this skill’s RUBE_MULTI_EXECUTE_TOOL for efficient batch operations, while ensuring the tool mode stays in sync with the latest API.

Quick Moxie Integration for Composio: If you’re adding Moxie support to AI agents or workflow systems, this skill provides an end-to-end path—from connection management to tool execution—including automated connection status checks and error handling.

Dynamic Tool Discovery and Execution: When the Moxie API toolset updates frequently, this skill enforces calling RUBE_SEARCH_TOOLS first to fetch the latest mode, preventing integration failures caused by hard-coded tool definitions.

Core Features

Intelligent Tool Discovery: Use RUBE_SEARCH_TOOLS to dynamically fetch the latest list of Moxie toolkit tools, input schemas, and recommended execution plans, ensuring your automation scripts always use currently valid API endpoints.

Connection Status Management: Use RUBE_MANAGE_CONNECTIONS to automatically check the Moxie connection status, verifying that the connection is ACTIVE before running tasks, and guiding the user through the authentication flow when needed.

Multi-Tool Batch Execution: Use RUBE_MULTI_EXECUTE_TOOL to execute multiple Moxie operations sequentially within a single session, supporting session reuse and memory management—ideal for complex workflow automation scenarios.

Frequently Asked Questions

What Configuration Does Rube MCP Require?

Rube MCP does not require an API key. Just add https://rube.app/mcp as an MCP server to use it. After connecting, you can initialize the Moxie integration by calling RUBE_MANAGE_CONNECTIONS and specifying the toolkit as moxie.

Why Must I Call RUBE_SEARCH_TOOLS First?

Composio tool modes change frequently. Hard-coding tool definitions can cause calls to fail. The response from RUBE_SEARCH_TOOLS includes the currently valid tool_slug, input parameter schemas, as well as known pitfalls and best practices—ensuring your automation scripts remain compatible.

How Do I Handle a Non-ACTIVE Moxie Connection?

After calling RUBE_MANAGE_CONNECTIONS, check the returned connection status. If the status is not ACTIVE, the response will include an authentication link. Complete authentication, then call the connection management interface again to confirm the status becomes ACTIVE before executing any Moxie tool actions.