What is RUBE MCP and how does it integrate with Mailcheck?

RUBE MCP is the Composio-managed control plane for toolkits. It provides APIs to discover tools, manage connections, and execute tools for Mailcheck workflows.

Why must I call RUBE_SEARCH_TOOLS before executing any tool?

Tool schemas change over time. Fetching current slugs and input schemas ensures you use valid arguments and avoid failures due to outdated configurations.

What should memory contain in RUBE_MULTI_EXECUTE_TOOL calls?

Include a memory object (even if empty) to preserve context across tool executions, as required by the core workflow pattern.

mailcheck-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Mailcheck Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/mailcheck

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Mailcheck operations through Composio's Mailcheck toolkit using Rube MCP. It always fetches current tool schemas with RUBE_SEARCH_TOOLS to prevent hardcoding slugs or args. Streamlined discovery, connection management, and execution enable reliable Mailcheck workflows.

How This Skill Works

The workflow discovers available tools with RUBE_SEARCH_TOOLS, then verifies the Mailcheck connection via RUBE_MANAGE_CONNECTIONS. Once a valid tool slug is selected, it executes the task with RUBE_MULTI_EXECUTE_TOOL, always including a memory payload and using a session_id to maintain continuity across steps.

When to Use It

You need to run a specific Mailcheck operation and must use the latest tool schemas.
Setting up or revalidating a Mailcheck connection before workflows.
Executing a discovered tool slug with arguments derived from the search results.
Coordinating multiple Mailcheck steps in a single session or workflow.
Diagnosing issues by validating active status and proper session reuse during Mailcheck automation.

Quick Start

Step 1: Add Rube MCP as an MCP server (https://rube.app/mcp) in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS with a Mailcheck use_case to fetch current tool slugs and input schemas.
Step 3: Use RUBE_MANAGE_CONNECTIONS to ensure the mailcheck toolkit is ACTIVE, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and a memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas before any execution.
Verify that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status prior to running tools.
Use exact field names and types from the tool schemas returned by RUBE_SEARCH_TOOLS.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even when empty.
Reuse session IDs within a workflow to maintain context and paginate responses as needed.

Example Use Cases

Set up a new Mailcheck connection via RUBE_MANAGE_CONNECTIONS and execute a scheduled inbox scan using the discovered tool slug.
Discover available Mailcheck tools for a 'domain reputation' task and run the matching tool with the correct input schema.
Perform bulk Mailcheck operations in a single session by iterating through discovered tool slugs with RUBE_MULTI_EXECUTE_TOOL.
Handle pagination from RUBE_SEARCH_TOOLS by continuing to fetch until all tool slugs and schemas are retrieved.
Debug a failed tool execution by checking the ACTIVE connection status and reusing the existing session ID.

Frequently Asked Questions

Add this skill to your agents