How to Sell SaaS With AI Agents Over MCP
You sell SaaS with an AI agent over MCP by connecting the agent to a billing platform's MCP server and asking it to create your plans, checkout and webhooks. Pocketsflow's MCP server gives Cursor, Claude Code, ChatGPT and Claude 293 tools, including subscriptions, usage billing, license keys and webhooks, and Pocketsflow is the merchant of record, so sales tax and VAT on every renewal are handled.
What "selling SaaS over MCP" means
MCP (Model Context Protocol) is an open standard that lets an AI app call tools in other software. When a SaaS founder connects Pocketsflow over MCP, the agent that writes the app's code can also set up the app's billing. You ask "create a Pro plan at $29 a month with a 14 day trial", and the agent calls Pocketsflow's create_subscription_offer tool. The plan exists in Pocketsflow seconds later, ready to sell.
The Pocketsflow MCP tools a SaaS needs
Four Pocketsflow tool groups cover most SaaS billing work. The chart counts the tools in each, read from Pocketsflow's MCP tool list.
| Point | Tools |
|---|---|
| Plans | 6 |
| Usage | 4 |
| Licenses | 5 |
| Webhooks | 6 |
Source: Pocketsflow's MCP server tool list (www.pocketsflow.com/mcp), October 2026.
- Plans (subscriptions): Pocketsflow's tools create plans and pause, resume or cancel a customer's subscription.
- Usage: Pocketsflow's tools set usage pricing, report usage and change seat counts. Usage-based pricing is part of the Pocketsflow Pro plan.
- Licenses: Pocketsflow's tools look up, disable, enable or reset the activations of a key, for one-time software sales.
- Webhooks: Pocketsflow's tools create a signed webhook to your app and send a test delivery.
Pocketsflow also has 9 retention tools that find subscriptions at risk and manage save offers, so the same agent can work on churn later.
How to set up SaaS billing with an agent
- Create a free Pocketsflow account. Plans, trials, webhooks and the MCP server need no paid plan.
- Switch the Pocketsflow dashboard to test mode, so you can try everything with no real money. Then connect your AI app to
www.pocketsflow.com/mcp, sign in and click Allow access: the connection stays in the mode the dashboard was in when you clicked Allow. - Ask: "Create Pro and Team plans, monthly and yearly, with a 14 day trial on Team."
- Ask: "Add a webhook to app.example.com/api/billing for subscription events and send a test." The agent calls
create_webhookandtest_webhook. - Ask the agent to write the webhook handler in your codebase: grant access on subscription created, warn on payment failed, downgrade on deleted. Pocketsflow signs every delivery, so the handler checks the signature.
- Ask: "Give me a checkout link for the Team plan." Put that link, or the embedded checkout, on your pricing page.
Why the coding agent should do billing too
A SaaS founder already asks Cursor or Claude Code to write the app. With Pocketsflow connected, the same agent sees both sides: it creates the plan in Pocketsflow and writes the code that listens to Pocketsflow's webhooks. Nothing is copied between a billing dashboard and the editor, so plan names and event names stay in step. Every change the agent makes in Pocketsflow also shows up in the Pocketsflow dashboard, where you can check it.
What a Pocketsflow agent cannot do
Pocketsflow keeps payouts and bank details out of the MCP server: an agent cannot withdraw your balance or change where you get paid. Each connection is a separate API key named "MCP: <app>", and deleting it disconnects that agent. An agent can cancel a subscription or issue a refund, so Pocketsflow's setup prompt tells it to ask you first.
What selling SaaS on Pocketsflow costs
| Cost | On Pocketsflow |
|---|---|
| Monthly fee | None on the free plan |
| Fee per payment | 4.7% + $0.30, card processing included |
| Sales tax and VAT on renewals | Collected and paid by Pocketsflow as merchant of record |
| MCP server | Included on every plan |
Your AI app has its own subscription. For the full plan list, see Pocketsflow pricing, and for everything Pocketsflow does for software, see billing for SaaS.
When another setup fits better
Pocketsflow suits founders who want tax handled and billing set up from their editor. A team that already has a billing engineer and registers for sales tax itself may prefer a payment processor's own billing product and API, and pay a lower fee per payment for that work. To start with Pocketsflow, follow the Cursor setup guide or the Claude Code setup guide.