Rube MCP is Composio's MCP server endpoint used to discover tool schemas and manage tool execution for 2chat workflows.

Why must I call RUBE_SEARCH_TOOLS first?

Tool slugs and input schemas change over time. RUBE_SEARCH_TOOLS fetches the current, schema-compliant definitions.

What if tool schemas change during a workflow?

Re-run RUBE_SEARCH_TOOLS to update slugs and field names, then proceed with RUBE_MULTI_EXECUTE_TOOL using the new schema.

-2chat-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

2chat Automation via Rube MCP

Automate 2chat operations through Composio's 2chat toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/_2chat

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate 2chat operations through Composio's 2chat toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas before execution and validating an ACTIVE connection to the _2chat toolkit, ensuring up-to-date tooling and fewer errors.

How This Skill Works

First, query available tools with RUBE_SEARCH_TOOLS to retrieve tool slugs and input schemas. Then establish and verify an ACTIVE connection to the _2chat toolkit using RUBE_MANAGE_CONNECTIONS. Finally, execute a selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments, a memory payload, and a session_id; always use the latest schemas from RUBE_SEARCH_TOOLS.

When to Use It

When you need to perform a 2chat operation and want to discover the latest tool schemas first
When setting up a Rube MCP connection for the _2chat toolkit and validating ACTIVE status
When executing tools, ensuring memory and session IDs are included as per the discovered schema
When tool schemas change or you need to navigate pagination in discovery results
When chaining multiple 2chat tools or performing bulk ops via RUBE_REMOTE_WORKBENCH

Quick Start

Step 1: Add the MCP endpoint https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["_2chat"] and confirm the session is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to find a 2chat tool slug, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, memory: {}, and a session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before any execution to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; avoid hardcoding
Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new tasks; handle pagination tokens

Example Use Cases

Discover a 2chat tool slug from RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL using the returned input fields.
Connect to the _2chat toolkit with RUBE_MANAGE_CONNECTIONS and run a workflow to fetch and process chat messages.
Handle pagination while discovering tools and continue fetching until all schemas are retrieved.
Run multiple 2chat tools in sequence using memory and a shared session_id via RUBE_MULTI_EXECUTE_TOOL.
Bulk run several 2chat operations with RUBE_REMOTE_WORKBENCH and run_composio_tool() for parallel execution.

Frequently Asked Questions

Add this skill to your agents