Crustdata Automation

What This Skill Does

• This skill automates Crustdata operations using Composio's Crustdata toolkit via Rube MCP.
• It's designed for users who need to programmatically interact with Crustdata for data management.
• The skill enables automated data manipulation and workflow integration with Crustdata.

When to Use

• Automate data imports.
• Schedule data backups.
• Manage data transformations.
• Trigger data exports.
• Cleanse and validate data.
• Monitor data quality.

Key Features

• Automates Crustdata tasks via Rube MCP.
• Uses RUBE_SEARCH_TOOLS for tool discovery.
• Requires active Crustdata connection.
• Employs RUBE_MULTI_EXECUTE_TOOL for execution.
• Provides connection status checks.
• Ensures schema compliance.

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• Crustdata Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/crustdata

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["crustdata"] 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

• Powered by Composio
• Crustdata Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/crustdata

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Crustdata connection via RUBE_MANAGE_CONNECTIONS with toolkit crustdata Always call RUBE_SEARCH_TOOLS first to get current tool schemas

• 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 crustdata If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Crustdata operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Crustdata task"}] session: {id: "existing_session_id"}

RUBE_MANAGE_CONNECTIONS toolkits: ["crustdata"] session_id: "your_session_id"

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

• 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

Powered by Composio