Can I use Ko-fi as a CLI?

Yes. KosmoKrator exposes a Ko-fi CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Ko-fi through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Ko-fi tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Ko-fi credentials stored?

Ko-fi credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Ko-fi MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Ko-fi CLI for AI Agents

Use the Ko-fi CLI from KosmoKrator to call Ko-fi tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Ko-fi CLI Setup

Ko-fi can be configured headlessly with `kosmokrator integrations:configure ko-fi`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure ko-fi --set access_token="$KO_FI_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor ko-fi --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`access_token`	`KO_FI_ACCESS_TOKEN`	Secret `secret`	yes	Access Token
`url`	`KO_FI_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call ko-fi.ko-fi_list_supporters '{"page":1,"limit":1}' --json

Provider shortcut

kosmo integrations:ko-fi ko-fi_list_supporters '{"page":1,"limit":1}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs ko-fi --json
kosmo integrations:docs ko-fi.ko-fi_list_supporters --json
kosmo integrations:schema ko-fi.ko-fi_list_supporters --json
kosmo integrations:search "Ko-fi" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`ko-fi.ko-fi_list_supporters`

List all supporters who have donated or subscribed to your Ko-fi page. Returns supporter names, emails, and contribution history.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call ko-fi.ko-fi_list_supporters '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_list_supporters '{"page":1,"limit":1}' --json

`ko-fi.ko-fi_get_supporter`

Get detailed information about a single Ko-fi supporter by their email address. Returns full supporter profile including contribution history and status.

Read read

Parameters: email

Generic call

kosmo integrations:call ko-fi.ko-fi_get_supporter '{"email":"example_email"}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_get_supporter '{"email":"example_email"}' --json

`ko-fi.ko-fi_list_transactions`

List all transactions on your Ko-fi page including donations, subscriptions, and shop orders. Returns transaction details with amounts and dates.

Read read

Parameters: type, page, limit

Generic call

kosmo integrations:call ko-fi.ko-fi_list_transactions '{"type":"example_type","page":1,"limit":1}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_list_transactions '{"type":"example_type","page":1,"limit":1}' --json

`ko-fi.ko-fi_list_commissions`

List all commission requests on your Ko-fi page. Returns commission details including status, requester info, and pricing.

Read read

Parameters: status, page, limit

Generic call

kosmo integrations:call ko-fi.ko-fi_list_commissions '{"status":"example_status","page":1,"limit":1}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_list_commissions '{"status":"example_status","page":1,"limit":1}' --json

`ko-fi.ko-fi_get_commission`

Get detailed information about a single Ko-fi commission by its ID. Returns full commission data including description, status, and requester details.

Read read

Parameters: commission_id

Generic call

kosmo integrations:call ko-fi.ko-fi_get_commission '{"commission_id":"example_commission_id"}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_get_commission '{"commission_id":"example_commission_id"}' --json

`ko-fi.ko-fi_list_shop_items`

List all items in your Ko-fi shop. Returns item names, descriptions, prices, and availability.

Read read

Parameters: page, limit

Generic call

kosmo integrations:call ko-fi.ko-fi_list_shop_items '{"page":1,"limit":1}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_list_shop_items '{"page":1,"limit":1}' --json

`ko-fi.ko-fi_get_current_user`

Get the profile of the currently authenticated Ko-fi user. Useful to verify the connection and see account details.

Read read

Parameters: none

Generic call

kosmo integrations:call ko-fi.ko-fi_get_current_user '{}' --json

Shortcut

kosmo integrations:ko-fi ko-fi_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

ko-fi.ko-fi_list_supporters 2 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_list_supporters --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of results per page (default: 25).

ko-fi.ko-fi_get_supporter 1 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_get_supporter --json

Parameter	Type	Required	Description
`email`	string	yes	The email address of the supporter to retrieve.

ko-fi.ko-fi_list_transactions 3 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_list_transactions --json

Parameter	Type	Required	Description
`type`	string	no	Filter by transaction type: donation, subscription, or shop_order.
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of results per page (default: 25).

ko-fi.ko-fi_list_commissions 3 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_list_commissions --json

Parameter	Type	Required	Description
`status`	string	no	Filter by commission status: pending, accepted, completed, or declined.
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of results per page (default: 25).

ko-fi.ko-fi_get_commission 1 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_get_commission --json

Parameter	Type	Required	Description
`commission_id`	string	yes	The ID of the commission to retrieve.

ko-fi.ko-fi_list_shop_items 2 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_list_shop_items --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`limit`	integer	no	Number of results per page (default: 25).

ko-fi.ko-fi_get_current_user 0 parameters

Schema command

kosmo integrations:schema ko-fi.ko-fi_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.