← All integrations

Ko-fi MCP server

1 operation4 webhooks

Payment notifications from Ko-fi - receive the webhook Ko-fi sends when a donation, membership payment, shop order or commission is paid, with every delivery verified against the account's token. Ko-fi publishes no REST API.

Try Ko-fi with your agent

Connect Ko-fi, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Ko-fi on my account, then run one read-only example and show me the result.

Runs once, when you ask

Ko-fi tools and triggers

Tools are what your agent can do in Ko-fi through Corsair's MCP server. Triggers are the Ko-fi events a routine can start from.

Webhooks

  • List EventsRead-only

    List the payment types Ko-fi can deliver, from its webhook reference; makes no API call, because Ko-fi has no REST API

    webhooks.listEvents

Connect Ko-fi to Claude, ChatGPT or Cursor

  1. 1

    Connect Ko-fi in Corsair

    Add your Ko-fi API key once in Corsair. Corsair stores the credential encrypted and makes the Ko-fi API calls for your agent, so it never goes into a prompt or a config file. Connect Ko-fi

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Ko-fi. On a ChatGPT personal plan, connect Ko-fi here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. Every Ko-fi operation only reads data, so it runs right away in every mode.

FAQ

Install corsair and @corsair-dev/kofi, add the Ko-fi plugin, and connect with an API key. Then call methods like corsair.kofi.api.webhooks.listEvents() from your app. Corsair verifies webhooks, and keeps each tenant isolated.

Yes. Ko-fi requires an API key from your Ko-fi account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Ko-fi, GitHub, Notion, Stripe, and the rest. Trigger Ko-fi from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for payment notifications from Ko-fi - receive the webhook Ko-fi sends when a donation, membership payment, shop order or commission is paid, with every delivery verified against the account's token. Ko-fi publishes no REST API. Common builds include sync jobs, admin tooling, and agents that call Ko-fi APIs from your backend. Webhook handlers react to Ko-fi events and fan out to Slack, email, or other plugins in the same tenant.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Ko-fi API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/kofi in the open repo. When Ko-fi ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Ko-fi data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Ko-fi data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Ko-fi on a link in Strict mode and every write waits for your approval, while destructive actions are refused. Every Ko-fi operation only reads data, so there are no changes to approve today. You can change a link's mode at hub.corsair.dev/me.