Rube MCP is a cloud-based automation framework from Composio that lets you discover, connect to, and run Stack Exchange tooling via standardized commands.

No. You add the MCP endpoint URL and the toolkit handles authentication during the connection step.

Why always search tools first?

Tool schemas change over time; fetching the latest tool slugs and input schemas ensures compatibility and prevents failures.

stack-exchange-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Stack Exchange Automation via Rube MCP

Automate Stack Exchange operations through Composio's Stack Exchange toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/stack_exchange

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["stack_exchange"]
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 Stack Exchange-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `stack_exchange`
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/stack-exchange-automation/SKILL.md

View on GitHub

Overview

Automate Stack Exchange operations using Composio's Stack Exchange toolkit through Rube MCP. This skill guides you to discover current tool schemas, connect to the Stack Exchange toolkit, and orchestrate tool executions in safe, repeatable workflows.

How This Skill Works

Start by discovering available tools with RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas. Then verify your Stack Exchange connection via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory, session_id, and the discovered arguments.

When to Use It

When you need to automate Stack Exchange operations via Composio using Rube MCP and need up-to-date tool schemas.
When you need to verify an ACTIVE connection to the stack_exchange toolkit before running workflows.
When you want to discover tools first to get the required input schemas before executing tasks.
When you need to execute tools with RUBE_MULTI_EXECUTE_TOOL and manage memory and session across steps.
When you handle large result sets and require pagination handling using provided tokens.

Quick Start

Step 1: Configure your client to use the MCP server by adding https://rube.app/mcp.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current tool schemas for Stack Exchange operations.
Step 3: Establish the connection with RUBE_MANAGE_CONNECTIONS, then execute a discovered tool using RUBE_MULTI_EXECUTE_TOOL with memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to fetch up-to-date tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results to maintain schema compliance.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and avoid hardcoding tool slugs.

Example Use Cases

Example: Discover available tools for Stack Exchange operations, then connect and run a specific tool to fetch new questions.
Example: Execute a discovered tool with an input payload that follows the returned schema.
Example: Use RUBE_MULTI_EXECUTE_TOOL in a loop with memory to perform daily moderation tasks.
Example: Bulk operations via RUBE_REMOTE_WORKBENCH with run_composio_tool for Stack Exchange workflows.
Example: Handle pagination by continuing to call tools until no more pages are returned.

Frequently Asked Questions

Add this skill to your agents