What is Rube MCP and why do I need it?

Rube MCP is the central MCP server you connect to (https://rube.app/mcp) to discover current tool schemas and coordinate tool execution for Discordbot tasks.

Why must I call RUBE_SEARCH_TOOLS before executing tools?

Tool schemas change over time. RUBE_SEARCH_TOOLS fetches up-to-date slugs and input schemas so you don't hardcode outdated parameters.

What if the Discordbot connection is not ACTIVE?

Follow the returned auth link to complete setup, then re-check with RUBE_MANAGE_CONNECTIONS until the status shows ACTIVE before running workflows.

What fields are required in the execute call?

You must supply memory (even if empty), session_id, tool_slug from the discovered results, and arguments that conform to the exact discovered schema.

discordbot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Discordbot Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/discordbot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Discordbot operations through Composio's Discordbot toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing a Discordbot connection, and executing tools in a session to ensure up-to-date, reliable workflows.

How This Skill Works

Begin by discovering available tools with RUBE_SEARCH_TOOLS to retrieve current slugs and input schemas. Then verify or establish a Discordbot connection using RUBE_MANAGE_CONNECTIONS with the discordbot toolkit, ensuring the status is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact schema-compliant arguments, a memory object, and a session_id.

When to Use It

You need to automate a Discordbot task and require up-to-date tool schemas before execution.
You want to run a sequence of Discordbot operations within a single session.
You must verify the Discordbot connection is ACTIVE before performing actions.
You are discovering available tools for a specific Discordbot use case and planning the execution flow.
You need to handle tool discovery, connection management, and execution without hardcoding slugs.

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with the discordbot toolkit and confirm ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen slug, proper memory, and a session_id.

Best Practices

Always search first with RUBE_SEARCH_TOOLS to get current tool schemas and slugs.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools.
Use exact field names and types from the discovered tool schemas; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow when possible; generate new IDs for new workflows.

Example Use Cases

Discover tools for Discordbot operations, select a slug, and prepare to run with the correct input schema.
Connect to the Discordbot toolkit and verify ACTIVE status before any tool execution.
Execute a sequence of tools in a single session using RUBE_MULTI_EXECUTE_TOOL with proper memory and arguments.
Handle pagination or new tool schemas by re-running RUBE_SEARCH_TOOLS to refresh tool slugs.
Post an automated message or fetch status by chaining tools within an active, reusable session.

Frequently Asked Questions

Add this skill to your agents