Ko-fi for AI agents
Ko-fi lets creators collect one-time donations, memberships, and shop sales from their audience, with support delivered as tips instead of traditional invoiced payments. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Ko-fi.
Log a new donation received
Record a Ko-fi payment notification into a spreadsheet or CRM as it arrives.
Flag a new membership signup
Notify a team channel when a Ko-fi payment webhook reports a new recurring member.
Read supporter activity only
Read recent Ko-fi payment events to summarize the week's donations for a creator update, without touching any payout.
1 Ko-fi actions, graded by risk.
Every Ko-fi action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
1Create and change things. Allow, or ask the user first.
- ko_fi.payment_webhook_postReceive Ko-fi payment webhook
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Ko-fi in three steps.
- 01Your users connect Ko-fiThey add their Ko-fi api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “receive Ko-fi payment webhook” can wait for the user to approve.
- 03Any agent can actYour agent calls Ko-fi through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ko_fi', { read: 'allow', write: 'ask', // payment_webhook_post destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ko-fi connects.
Users add their Ko-fi api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Ko-fi connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Ko-fi from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore finance and accounting apps.
Ko-fi and Arc0, answered.
Can I use Ko-fi with Claude, ChatGPT or Cursor?
Yes. Connect Ko-fi to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Ko-fi actions you allow.
How do users connect Ko-fi?
Users add their Ko-fi api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Ko-fi actions can my agent take?
1 in total: 0 read, 1 write and 0 destructive, such as “receive Ko-fi payment webhook”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Ko-fi?
Yes. Allow read actions and deny writes in the Ko-fi policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Ko-fi too?
Yes. The same Ko-fi connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ko-fi into your agent.
Your users connect Ko-fi once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan