What is Rube MCP used for in this skill?

Rube MCP acts as the Composio MCP server that enables tool discovery and execution for Shipengine tasks.

Why must I search tools first every time?

Tool schemas change over time; searching ensures you use current slugs and argument structures rather than hardcoded values.

How should I structure execution calls?

Ensure you call RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, the exact schema-compliant arguments, a memory object, and an active session_id.

shipengine-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Shipengine Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/shipengine

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Shipengine operations through Composio's Shipengine toolkit using Rube MCP. This workflow emphasizes discovering current tool schemas before execution and maintaining an active Shipengine connection for reliable automation.

How This Skill Works

Connect to Rube MCP, then discover available Shipengine tools with RUBE_SEARCH_TOOLS to fetch current schemas. Validate the Shipengine connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, ensuring a memory object and session ID are included for proper state management.

When to Use It

You need to automate a Shipengine task and must use the latest tool schemas before execution.
You want to establish or refresh an active Shipengine connection via Rube MCP before running workflows.
You intend to run multiple Shipengine tools in a single workflow using a shared session.
You are building a workflow and want to reuse session IDs across steps while maintaining continuity.
You need to discover all available tools (including handling pagination) before selecting specific actions.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client; no API keys needed.
Step 2: Verify RUBE_SEARCH_TOOLS responds, then call RUBE_MANAGE_CONNECTIONS with toolkit 'shipengine' and ensure ACTIVE status.
Step 3: Run a workflow: RUBE_SEARCH_TOOLS to find a tool, then RUBE_MULTI_EXECUTE_TOOL with memory and a session_id from the search results.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas and avoid hardcoding slugs or parameters.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing any tools.
Ensure schema compliance by using exact field names and types from the search results.
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and generate new ones for new workflows; watch for pagination tokens in tool lists.

Example Use Cases

Discover Shipengine tools with RUBE_SEARCH_TOOLS, then execute a label creation or rate quote tool using RUBE_MULTI_EXECUTE_TOOL within an ACTIVE connection.
Create a multi-step automation: discover tools, validate connection, then execute several tools in sequence in a single session.
Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk Shipengine operations across multiple orders.
Fetch the full tool schemas via RUBE_GET_TOOL_SCHEMAS and adapt your arguments to the exact schemaRef fields.
Handle pagination tokens during discovery to build a complete, reusable Shipengine automation workflow.

Frequently Asked Questions

Add this skill to your agents