Ko Fi Automation

What This Skill Does

This skill automates Ko Fi operations using Composio's Ko Fi toolkit through Rube MCP. It's designed for users who need to manage their Ko Fi account and integrate it with other systems. The skill requires an active Ko Fi connection and familiarity with Rube MCP.

When to Use

• Discover available Ko Fi tools.
• Check the status of the Ko Fi connection.
• Execute specific Ko Fi tools.
• Automate donation tracking.
• Manage Ko Fi posts.
• Integrate Ko Fi with other services.

Key Features

• Uses Rube MCP to automate Ko Fi operations.
• Requires an active Ko Fi connection.
• Relies on RUBE_SEARCH_TOOLS for tool discovery.
• Provides a core workflow pattern for execution.
• Offers documentation for the Ko Fi toolkit.
• Emphasizes the importance of schema compliance.

Manual Installation

Ko Fi Automation via Rube MCP

Automate Ko Fi operations through Composio's Ko Fi toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ko_fi

Prerequisites

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

Step 2: Check Connection

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