What must be configured to use mocean-automation?

Rube MCP must be connected; a Mocean connection must be ACTIVE; RUBE_SEARCH_TOOLS must respond to fetch current tool schemas.

Why is 'Always search first' emphasized?

Tool slugs and input schemas change; relying on cached definitions leads to failures; fetch fresh schemas before executing.

What should I do if the connection isn't ACTIVE?

Follow the returned auth link to complete setup, then re-check; you cannot run workflows until ACTIVE.

mocean-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/mocean-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Mocean Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mocean

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["mocean"]
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 Mocean-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `mocean`
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/mocean-automation/SKILL.mdView on GitHub

Overview

Automate Mocean operations using Composio's Mocean toolkit through Rube MCP. Start by discovering current tool schemas with RUBE_SEARCH_TOOLS, then connect to Mocean and execute tools. This approach makes workflows repeatable and keeps schemas up to date.

How This Skill Works

It works by first discovering available Mocean tools with RUBE_SEARCH_TOOLS, then establishing or validating an ACTIVE Mocean connection via RUBE_MANAGE_CONNECTIONS. Once a tool slug and its required arguments are known, it executes the tool using RUBE_MULTI_EXECUTE_TOOL, supplying a session and a memory payload as required.

When to Use It

Automating repeatable Mocean tasks with up-to-date tool schemas.
When tool schemas change frequently and you must fetch the latest definitions before execution.
When you need to ensure an ACTIVE Mocean connection prior to running workflows.
When orchestrating multiple Mocean tools in a single session with memory and state reuse.
When bulk or bulk-like Mocean operations are needed and you want to leverage RUBE_MULTI_EXECUTE_TOOL.

Quick Start

Step 1: Add the Mocean MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'mocean' and ensure the status is ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it via RUBE_MULTI_EXECUTE_TOOL using a session_id and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; manage pagination tokens if present.

Example Use Cases

Discover Mocean tools, connect, and execute a single 'send_sms' tool using the discovered slug.
Orchestrate a campaign workflow that sequences 'precheck', 'send_sms', and 'log_delivery' tools within one session.
Bulk-run several Mocean operations by executing multiple tool slugs in a single RUBE_MULTI_EXECUTE_TOOL call.
Monitor connection status and re-authenticate if ACTIVE becomes inactive during a workflow.
Fetch the latest tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt to changes in integration.

Frequently Asked Questions

Add this skill to your agents