Do I need API keys to use Rev AI automation with Rube MCP?

No API keys are required. You simply add the MCP server endpoint and connect the Rev AI toolkit.

What if tool slugs or schemas change?

Always call RUBE_SEARCH_TOOLS first to get the current slugs and input schemas; do not hardcode values.

How do I ensure a successful run?

Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools and include a memory object in RUBE_MULTI_EXECUTE_TOOL calls.

rev-ai-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Rev AI Automation via Rube MCP

Automate Rev AI operations through Composio's Rev AI toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/rev_ai

Prerequisites

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

Step 2: Check Connection

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

Overview

Rev AI Automation via Rube MCP lets you orchestrate Rev AI operations through Composio's Rev AI toolkit. It relies on dynamic tool discovery with RUBE_SEARCH_TOOLS and an active Rev AI connection, so you always use current schemas instead of hard coding slugs.

How This Skill Works

First, discover tools with RUBE_SEARCH_TOOLS to obtain slugs and input schemas. Then verify the Rev AI connection with RUBE_MANAGE_CONNECTIONS, and finally execute tools with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slugs and the required memory payload; always pass a session_id and keep memory as an object even if empty.

When to Use It

When you want to run Rev AI operations using current, tool discovered schemas
When you must validate an active Rev AI connection before workflows
When orchestrating multi step Rev AI tasks in a single session
When you need to reuse a session ID across a workflow and start a new one for new tasks
When you need to handle pagination or updates to tool schemas returned by RUBE_SEARCH_TOOLS

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm available Rev AI tools
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits set to rev_ai, then execute tools with RUBE_MULTI_EXECUTE_TOOL using a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results; do not guess
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty
Reuse session IDs within a workflow and generate new ones for new tasks

Example Use Cases

Discover Rev AI transcription tool slugs via RUBE_SEARCH_TOOLS and execute a transcription task
Connect Rev AI with RUBE_MANAGE_CONNECTIONS and run a sequence for video captioning
Run a batch Rev AI operation using RUBE_MULTI_EXECUTE_TOOL with a shared memory payload
Perform bulk Rev AI operations using RUBE_REMOTE_WORKBENCH run_composio_tool
Fetch updated tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt tool calls accordingly

Frequently Asked Questions

Add this skill to your agents