Jigsawstack Automation

What This Skill Does

This skill automates Jigsawstack operations using Composio's Jigsawstack toolkit through Rube MCP. It enables users to interact with and manage Jigsawstack resources, facilitating data integration and workflow automation. It is designed for users familiar with Rube MCP and the Composio ecosystem.

When to Use

Automating data transformations using Jigsawstack. Orchestrating complex data workflows. Integrating Jigsawstack with other systems. Managing Jigsawstack resources programmatically. Building custom data pipelines. Monitoring the performance of Jigsawstack workflows.

Key Features

Automates Jigsawstack operations via Rube MCP. Uses Composio's Jigsawstack toolkit. Requires an active Jigsawstack connection. Discovers available tools using RUBE_SEARCH_TOOLS. Checks connection status with RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

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

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

Toolkit docs: composio.dev/toolkits/jigsawstack

Prerequisites

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

Step 2: Check Connection

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

's Jigsawstack toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/jigsawstack

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

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