What is Rube MCP and why is it required?

Rube MCP is the integration layer used to connect to the V0 toolkit; you must connect via the v0 toolkit and use RUBE_SEARCH_TOOLS to fetch current schemas.

Why should I always call RUBE_SEARCH_TOOLS first?

Tool schemas change over time; fetching current schemas prevents using stale slugs or mismatched input fields.

What if the connection is not ACTIVE?

Do not execute tools. Complete the authentication flow via the provided auth link and recheck that the connection shows ACTIVE before running workflows.

v0-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

V0 Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/v0

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates V0 operations through Composio's V0 toolkit using Rube MCP. It emphasizes always searching for current tool schemas before execution to avoid stale slugs and input fields.

How This Skill Works

You connect to the V0 toolkit via Rube MCP, then follow a three-step workflow: discover available tools with RUBE_SEARCH_TOOLS, verify an ACTIVE V0 connection with RUBE_MANAGE_CONNECTIONS, and execute chosen tools with RUBE_MULTI_EXECUTE_TOOL using the proper memory payload and a session_id. This approach ensures up-to-date schemas and robust session handling.

When to Use It

Automating recurring V0 operations while keeping tool schemas up to date
Adapting to changes in tool slugs or input fields by re-discovering tools first
Ensuring an ACTIVE V0 connection before running workflows
Orchestrating multi-tool V0 sequences within a single session
Performing bulk V0 operations using RUBE_REMOTE_WORKBENCH when supported

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds
Step 2: Connect to the v0 toolkit with RUBE_MANAGE_CONNECTIONS and ensure the session is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your V0 task, then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first 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 a session_id within a workflow and generate new ones for separate tasks; watch pagination

Example Use Cases

Discover tools for a V0 operation and execute a single TOOL_SLUG with an existing session_id and empty memory
Chain two tools in one session: discover, verify connection, then execute TOOL_SLUG_A followed by TOOL_SLUG_B
Reuse the same session_id to execute multiple discovered tools sequentially
Adapt to tool changes by re-fetching latest schemas before updating an automation script
Bulk execute multiple tools via RUBE_REMOTE_WORKBENCH using run_composio_tool

Frequently Asked Questions

Add this skill to your agents