PromptShop

Melo Automation

Automate Melo user provisioning and workflows via Rube MCP.

Install

npx promptshop add melo-automation

Details

What This Skill Does

This skill automates Melo operations using the Composio Melo toolkit through Rube MCP. It's designed for users who need to streamline their Melo workflows by leveraging automated tools. The skill ensures proper setup, tool discovery, and execution while avoiding common pitfalls.

When to Use

Automate user provisioning in MeloSync data between Melo and other systemsTrigger workflows based on Melo eventsManage Melo configurations programmaticallyMonitor Melo performance metricsCreate reports based on Melo data

Key Features

Automates Melo operations via Rube MCPUses Composio's Melo toolkitRequires Rube MCP and Melo connectionDiscovers tools using RUBE_SEARCH_TOOLSChecks connection status with RUBE_MANAGE_CONNECTIONSExecutes tools with RUBE_MULTI_EXECUTE_TOOL

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedMelo Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/melo

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Melo connection via RUBE_MANAGE_CONNECTIONS with toolkit melo 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit melo 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: "Melo 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 Melo task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["melo"] 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Melo-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit melo
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

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

Toolkit docs: composio.dev/toolkits/melo