What is Rube MCP and how do I set it up?

Rube MCP is Composio's MCP server. Add the endpoint https://rube.app/mcp to your client configuration; no API keys are needed.

Why must I always search tools first?

Tool schemas can change. Always fetch current schemas before building or executing workflows to avoid mismatched inputs.

When should I ensure ACTIVE connection?

Before executing any tool, verify via RUBE_MANAGE_CONNECTIONS that the Vestaboard toolkit connection is ACTIVE.

vestaboard-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Vestaboard Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/vestaboard

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Vestaboard operations using Composio's Vestaboard toolkit via Rube MCP. It relies on live tool schemas discovered at runtime and requires an active Vestaboard connection. Always start workflows by discovering tools to fetch current inputs and plans.

How This Skill Works

Begin by discovering available tools with RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and execution plans. Then verify an ACTIVE Vestaboard connection with RUBE_MANAGE_CONNECTIONS before executing any tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool slug and a memory object. For more complex flows, reuse session IDs and handle pagination as needed.

When to Use It

You need to automate posting messages to Vestaboard from a data-driven trigger.
You must fetch current tool schemas before composing a Vestaboard workflow.
You want to validate an ACTIVE Vestaboard connection prior to execution.
You want to run a sequence of Vestaboard actions using a shared session.
You need to perform bulk Vestaboard updates across multiple displays.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys).
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Vestaboard tool slugs and input schemas.
Step 3: Run RUBE_MANAGE_CONNECTIONS (toolkits: ["vestaboard"]). If ACTIVE, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Check RUBE_MANAGE_CONNECTIONS returns ACTIVE before running tools.
Use exact field names and types from tool schemas; avoid hardcoding slugs.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and monitor pagination tokens.

Example Use Cases

Daily status update: discover tool, ensure ACTIVE connection, then execute with today's status payload.
Standup recap: fetch tool schemas, ensure ACTIVE, and push the latest notes to Vestaboard.
Bulk display across boards: reuse a single session and run the same tool across multiple displays.
Onboarding test: connect the Vestaboard toolkit, authenticate via the provided link, then run a test message.
Tool discovery workflow: list available Vestaboard actions and capture slugs for a monitoring dashboard.

Frequently Asked Questions

Add this skill to your agents