Imagekit Io Automation

What This Skill Does

• This skill automates operations within Imagekit IO using Composio's Imagekit IO toolkit via Rube MCP.
• It's designed for users who want to streamline their image management workflows and integrate them with other systems.
• The skill simplifies tasks by providing tools for discovering, connecting to, and executing Imagekit IO functions.

When to Use

• Automate image optimization tasks.
• Manage image transformations automatically.
• Integrate Imagekit IO with other platforms.
• Schedule regular image backups.
• Trigger actions based on image metadata.
• Simplify image delivery workflows.

Key Features

• Automates Imagekit IO operations via Rube MCP.
• Uses Composio's Imagekit IO toolkit.
• Requires an active Imagekit IO connection.
• Employs RUBE_SEARCH_TOOLS for tool discovery.
• Provides a core workflow pattern for execution.
• Offers guidance on avoiding common pitfalls.

Manual Installation

Imagekit IO Automation via Rube MCP

Automate Imagekit IO operations through Composio's Imagekit IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/imagekit_io

Prerequisites

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

Step 2: Check Connection

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