What is RUBE MCP in this context?

RUBE MCP is the Composio-based MCP framework used to automate external toolchains. You connect, discover, and execute tools via RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.

Why must I search tools first?

Tool schemas change frequently. Always fetching current schemas prevents hardcoding slugs or arguments that may be outdated.

What should I include in the memory parameter during execution?

Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it's an empty object ({}), to maintain state and support multi-step workflows.

opengraph-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Opengraph IO Automation via Rube MCP

Automate Opengraph IO operations through Composio's Opengraph IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/opengraph_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["opengraph_io"]
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 Opengraph IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `opengraph_io`
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/opengraph-io-automation/SKILL.md

View on GitHub

Overview

Automate Opengraph IO tasks through Composio's toolkit using Rube MCP. The workflow emphasizes discovering current tool schemas before execution to prevent drift and ensure compatibility.

How This Skill Works

The skill starts by using RUBE_SEARCH_TOOLS to fetch live Opengraph IO tool schemas. It then establishes a connection with RUBE_MANAGE_CONNECTIONS for the opengraph_io toolkit and executes workflows via RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and a memory payload.

When to Use It

When you need end-to-end Opengraph IO automation within a Composio workflow.
When tool schemas may change and you must fetch current slugs before running tasks.
When connecting to Opengraph IO for the first time or re-authenticating an existing connection.
When running bulk or sequenced Opengraph IO operations that require orchestration.
When diagnosing failures, including session reuse and pagination handling.

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'opengraph_io' and activate the connection.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a test using RUBE_MULTI_EXECUTE_TOOL with memory: {}.

Best Practices

Always call RUBE_SEARCH_TOOLS first to retrieve current tool schemas.
Verify the connection status via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE before execution.
Use exact field names and types from the tool schemas in your RUBE_MULTI_EXECUTE_TOOL calls.
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL, even if empty ({}).
Reuse session IDs within a workflow and paginate responses as needed.

Example Use Cases

Automate bulk OG meta tag updates for a list of URLs and publish changes.
Validate and publish OG data after CMS edits by routing tasks through the opengraph_io toolkit.
Discover tools, connect, and execute a sequence of OG operations for a marketing campaign.
Automate re-authentication flows if a connection becomes inactive and re-establish it.
Audit OpenGraph IO tasks by fetching schemas, executing tools, and handling pagination tokens.

Frequently Asked Questions

Add this skill to your agents