What is Rube MCP and how does it relate to Linkhut automation?

Rube MCP is an MCP server integration used to discover, manage, and execute Linkhut tools. It provides commands like RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL to orchestrate Linkhut workflows.

Do I always need to search tools before running a workflow?

Yes. Always calling RUBE_SEARCH_TOOLS fetches the current tool schemas and avoids hardcoding slugs or argument names.

How should session IDs be managed across a workflow?

Reuse the same session_id for related steps within a workflow and generate a new one for independent workflows. This enables progress tracking and proper memory handling.

linkhut-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Linkhut Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/linkhut

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Linkhut operations through Composio's Linkhut toolkit via Rube MCP. Always search tool schemas first to ensure you use current tool slugs and inputs.

How This Skill Works

This skill discovers available Linkhut tools using RUBE_SEARCH_TOOLS, checks that the Linkhut connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, and then executes chosen tools with RUBE_MULTI_EXECUTE_TOOL, passing the required arguments and a memory object. Tool schemas and execution plans are retrieved first to avoid hardcoding.

When to Use It

Start a new Linkhut workflow and fetch current tool schemas
Run a workflow where tool schemas may have changed
Verify the Linkhut connection is ACTIVE before executing tools
Execute multiple tools in a single session using memory
Perform bulk or iterative tasks that require updated tool schemas (handle pagination)

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS for the linkhut toolkit and ensure status ACTIVE
Step 3: Run RUBE_SEARCH_TOOLS to discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas and known pitfalls
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from search results; avoid hardcoding slugs
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session_id within a workflow; generate new IDs only for new standalone workflows

Example Use Cases

Discover a Linkhut tool slug from RUBE_SEARCH_TOOLS and execute it with discovered arguments
Check connection and run a sequence of Linkhut tools in one session with memory
Iteratively fetch updated tool schemas before a large run using RUBE_SEARCH_TOOLS
Perform bulk Linkhut actions via RUBE_MULTI_EXECUTE_TOOL with multiple tool executions
Bulk operations using RUBE_REMOTE_WORKBENCH and run_composio_tool() for scalable tasks

Frequently Asked Questions

Add this skill to your agents