Ko-fi

@Ko-fi show me my supporter activity from the last 30 days including one-time donations and memberships

In the last 30 days, you received 47 transactions totaling $1,240. This breaks down to 32 one-time donations (average $18.50), 12 new monthly memberships at the $5 tier, and 3 membership renewals. Your top supporter contributed $100. Peak activity occurred on March 15th with 9 transactions. This example reflects typical Ko-fi API data structure; actual results depend on your account's transaction history.

Ko-fi's API provides transaction-level detail but doesn't expose supporter email addresses or personal info without explicit consent. Rate limits apply to frequent polling. This read-only example is safe for regular check-ins but won't modify your Ko-fi settings or send messages to supporters.

@Ko-fi create a new shop item for my digital art pack priced at $12 with a download link and set inventory to 50 copies

Shop item created successfully. Your 'Digital Art Pack' is now live at ko-fi.com/yourpage/shop with a $12 price point and 50-unit inventory cap. The download link you provided will be delivered automatically after purchase. Item ID: shop_item_8x7k2m. This example assumes your Ko-fi account has shop features enabled; the actual API response includes the full item URL and management endpoints.

Creating shop items requires an API key with write permissions. Ko-fi doesn't validate your download link's accessibility—test it manually before going live. Inventory tracking is automatic, but the MCP won't notify you when stock runs low. Consider pairing this with a read prompt to monitor sales velocity.

@Ko-fi analyze my supporter growth trends and draft a thank-you post highlighting the milestone we just hit

Your supporter count grew 34% quarter-over-quarter, crossing 500 total supporters last week. Monthly recurring revenue is up 28% to $2,100. Draft post: 'We just hit 500 supporters! 🎉 Your Ko-fi donations and memberships make this work sustainable. Special shoutout to everyone who joined this month—you're fueling the next big project. More updates coming soon!' This synthesis combines Ko-fi metrics with AI-generated messaging; review tone before posting.

This example pairs Ko-fi's transaction data with the AI's content generation. The MCP provides raw numbers; the AI interprets trends and drafts copy. Ko-fi doesn't auto-post to your page—you'll need to manually publish the thank-you message. Useful for regular community updates without manual spreadsheet work.

When Ko-fi MCP makes sense for small creator collectives

A three-person podcast team running a Patreon-style membership on Ko-fi wants to check supporter counts and recent donations during monthly planning calls. The Ko-fi MCP pulls membership data and transaction history into Switchy so the team can reference real numbers without tab-switching. This works if you're checking revenue trends or supporter milestones a few times a week. The trade-off: Ko-fi's API is read-only for most endpoints, so you can't automate thank-you messages or update tier descriptions from Switchy. If your workflow is mostly about pulling reports to inform decisions, the MCP saves the context-switch tax. If you need two-way automation, you'll still be opening the Ko-fi dashboard.

Why this MCP is borderline for thank-you workflows

A solo game developer wants to thank new Ko-fi supporters within an hour of their donation. The MCP can surface recent transactions in Switchy, but it won't send emails or post updates back to Ko-fi. You'd still need to copy supporter names into your email tool or social scheduler. This is useful if you're batching thank-yous at the end of each day and want all your context in one place. It's not useful if you expect the AI to draft and send acknowledgments automatically. The threshold: if you're checking Ko-fi once a day and manually writing notes, the MCP consolidates your workspace. If you want end-to-end automation, you need Zapier or a custom script on top of this.

When Ko-fi MCP fits campaign progress tracking

A four-person advocacy org runs a Ko-fi campaign to fund a documentary. The team checks progress twice a week to decide when to post milestone updates on social media. The Ko-fi MCP lets them query current totals and recent donor activity without leaving Switchy, so the comms lead can draft updates with live numbers in the same chat. This works if your cadence is weekly or bi-weekly and you're comfortable with read-only data. It doesn't work if you need real-time alerts or want to update campaign copy directly through the API. If your workflow is 'check numbers, write update, post elsewhere,' the MCP cuts two steps. If you need push notifications or write-back, it's not enough on its own.