Supadata Automation

What This Skill Does

This skill automates interactions with Supadata using Composio's toolkit and Rube MCP. It's designed for developers and data engineers who need to programmatically manage Supabase databases. The skill streamlines the process of discovering tools, managing connections, and executing workflows.

When to Use

• Create database backups automatically.
• Restore databases from backups.
• Manage database schemas programmatically.
• Automate data migrations.
• Monitor database performance.
• Scale database resources based on demand.

Key Features

• Discovers available Supadata tools via Rube MCP.
• Manages Supadata connections through Rube MCP.
• Executes Supadata tools with schema validation.
• Provides a structured workflow for tool execution.
• Handles authentication and connection status checks.
• Offers error handling and schema compliance guidance.

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