Spondyr Automation

What This Skill Does

The Spondyr Automation skill allows users to automate operations within the Spondyr platform via the Composio Rube MCP integration. It is designed for users who need to manage and interact with Spondyr programmatically. The skill leverages Rube MCP to discover and execute Spondyr tools.

When to Use

• Automate data extraction from Spondyr.
• Trigger Spondyr workflows based on external events.
• Manage Spondyr configurations programmatically.
• Integrate Spondyr with other systems.
• Monitor Spondyr activity and performance.
• Schedule routine Spondyr maintenance tasks.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Spondyr connection.
• Employs RUBE_SEARCH_TOOLS to dynamically find available tools.
• Utilizes RUBE_MANAGE_CONNECTIONS to manage the Spondyr connection.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides a structured workflow for Spondyr automation.

Manual Installation

Spondyr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spondyr

Prerequisites

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

Step 2: Check Connection

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