What is Supadata automation via Rube MCP?

It automates Supadata tasks by using Composio's Rube MCP toolkit to discover, connect, and execute Supadata tools.

Do I need API keys for this setup?

No API keys are needed. Just add the MCP endpoint (https://rube.app/mcp) as a server in your client configuration.

What must be verified before running a workflow?

Ensure RUBE_SEARCH_TOOLS is available, the Supadata connection is ACTIVE via RUBE_MANAGE_CONNECTIONS, and include a memory object in RUBE_MULTI_EXECUTE_TOOL calls.

supadata-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Supadata Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/supadata

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Supadata operations through Composio's Rube MCP toolkit. It requires an active Supadata connection and that RUBE_SEARCH_TOOLS is called first to fetch current tool schemas. This skill streamlines discovery, connection validation, and execution of Supadata tools.

How This Skill Works

Connect to Rube MCP and call RUBE_SEARCH_TOOLS to fetch tool schemas for Supadata tasks. Validate the connection with RUBE_MANAGE_CONNECTIONS, then execute discovered tools via RUBE_MULTI_EXECUTE_TOOL, including memory and session_id. Always rely on live tool schemas rather than hardcoding tool slugs or arguments, and ensure the connection remains ACTIVE during workflows.

When to Use It

When automating a Supadata task end-to-end and you need up-to-date tool schemas.
When setting up a new Supadata workflow from scratch using discovery results.
When validating the Supadata connection is ACTIVE before running workflows.
When executing multiple tools in sequence or in bulk via RUBE_MULTI_EXECUTE_TOOL.
When troubleshooting tool changes or schema updates by re-running RUBE_SEARCH_TOOLS to refresh.

Quick Start

Step 1: Get Rube MCP and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["supadata"] to connect.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then run RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug and memory.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tools to get current schemas.
Never hardcode tool slugs or argument schemas; rely on live results from the search.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running workflows.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({ }).
Reuse session IDs within a workflow; generate new ones for new workflows and watch for pagination.

Example Use Cases

Discover tools for a specific Supadata task, establish a connection, and execute the chosen tool with proper arguments.
After a schema update, re-run RUBE_SEARCH_TOOLS to fetch new arguments and adjust your automation accordingly.
Run a sequence of tools in a single session using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slugs.
Perform a bulk Supadata operation by combining RUBE_MULTI_EXECUTE_TOOL with RUBE_REMOTE_WORKBENCH for multiple tasks.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to verify compatibility before automation.

Frequently Asked Questions

Add this skill to your agents