What is Rube MCP in prerender automation?

Rube MCP is the centralized control plane that discovers tools, manages connections, and executes prerender tasks via tool slugs discovered at runtime.

Why must I always search tools first?

Tool schemas change; you should fetch current slugs and argument schemas to ensure compatibility and avoid hard-coded values.

How do I verify and maintain an ACTIVE prerender connection?

Use RUBE_MANAGE_CONNECTIONS with toolkit prerender to check status; if not ACTIVE, follow the returned auth link to complete setup and retry.

prerender-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Prerender Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/prerender

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Prerender operations through Composio's Prerender toolkit via Rube MCP. Always search tools first for current schemas to stay in sync with updates. This skill handles tool discovery, connection validation, and execution of prerender tasks.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to discover available prerender tools and their schemas. Then it uses RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE prerender connection. Finally, it runs the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered arguments and a memory payload.

When to Use It

When starting a prerender workflow for a new site or page, ensure you fetch current tool schemas first.
When tool schemas change or you need the latest execution plans, re-discover with RUBE_SEARCH_TOOLS before running.
When performing bulk prerender operations across multiple pages, use discovered tool slugs rather than hard-coded values.
When you need to validate or re-establish the prerender connection before executing tasks.
When auditing prerender jobs and needing to paginate through tool lists for full coverage.

Quick Start

Step 1: Verify RUBE MCP config and that RUBE_SEARCH_TOOLS is responsive.
Step 2: Connect to prerender via RUBE_MANAGE_CONNECTIONS with toolkit prerender and ensure status ACTIVE.
Step 3: Discover a tool with RUBE_SEARCH_TOOLS and run it with RUBE_MULTI_EXECUTE_TOOL using memory and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from search results (schema compliance).
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Auto-refresh prerender on a product page after CMS update.
Bulk prerender of a set of landing pages for a marketing campaign.
On-demand prerender scheduling when new content goes live.
Audit prerender pipelines after tool schema changes and verify compatibility.
Migrate prerender tasks between environments with consistent sessions.

Frequently Asked Questions

Add this skill to your agents