Build your Pocketsflow integration with Cursor's agent.
With Pocketsflow in Cursor's MCP settings, the agent stops guessing your product ids. It reads your real catalog, opens a checkout session to test with and registers the webhook your route handles, in the same chat where it writes the code.
- Connects via
- MCP server in settings
- Works in
- Cursor app, in the editor
- Plan
- Free plan with limited agent requests. Paid plans: Plus, Premium, Super, Ultra and Teams.
From an ask in Cursor to your store and back.
You type in Cursor. It calls a Pocketsflow tool, your store changes or answers, and the result comes back to the chat.
How an ask in your AI app becomes a change in your store:
- Cursor: “Send refunds to my server at /refunds.” The Pocketsflow MCP server checks the key you approved, calls create_webhook, and answers: “Done. Every refund now posts to your server at /refunds, signed with a new secret.”
- Cursor: “Which webhooks are live?” The Pocketsflow MCP server checks the key you approved, calls list_webhooks, and answers: “Two: Community invites on order.completed, and Refunds on order.refunded.”
- Cursor: “A Brand Kit checkout that returns to my app.” The Pocketsflow MCP server checks the key you approved, calls create_checkout_session, and answers: “Here is the Brand Kit checkout, $100.00. Paid buyers land on /thanks in your app.”
Connect Cursor in 3 steps.
Add the server
In Cursor's settings, open MCP and add a new server, or paste the config below into
~/.cursor/mcp.json(or.cursor/mcp.jsonfor one project).Allow access
Cursor opens Pocketsflow. Sign in to Pocketsflow and click Allow access. Pocketsflow adds a key named
MCP: <app>under Developers → API keys, in the mode your dashboard is in (live or test).Ask the agent
In chat, in Agent mode, Cursor lists the Pocketsflow tools and runs them as your account.
{
"mcpServers": {
"pocketsflow": {
"url": "https://www.pocketsflow.com/mcp"
}
}
}Server address https://www.pocketsflow.com/mcp
What to ask Cursor.
Write it the way you would ask a colleague. Under each ask are the Pocketsflow tools it calls.
“List my products and use the real ids in the pricing component.”
Reads your catalog, then edits your code.
- list_products
“Open a test checkout session for the Pro plan.”
Returns a checkout URL you can click through.
- create_checkout_session
“Send refunds to my server at /refunds.”
Adds a webhook for refund events with a signing secret.
- create_webhook
“Add 5 seats to Acme's team plan.”
Changes the seat count on their subscription.
- update_subscription_seats
“Show me the webhooks I already have.”
Lists endpoints, events and whether they are active.
- list_webhooks
What it can and can't do.
Connecting an AI is not handing over the keys. You approve it, you see every change, and you can unplug it in one click.
It can
- Use the same 303 tools as the public API: products, checkout links, discounts, upsells, orders, customers, subscriptions, license keys, usage billing, webhooks, newsletters and analytics.
- Read your payouts: what is ready to withdraw, what is still clearing, and why a payout is on hold.
- Set the refund policy buyers see at checkout, and look up any order's payment, fees and tax.
- Work in test mode with no real money, if your dashboard is in test mode when you click Allow.
It can't
- Refund a payment or withdraw money. Refunds and withdrawals stay in your dashboard.
- Connect without you: nothing happens until you sign in to Pocketsflow and click Allow access.
- See another store. Every call is scoped to the account you approved.
- Use a paid feature your plan lacks. It gets a clear error and tells you which plan unlocks it.
The setup prompt asks the agent to check with you before anything goes live, and every change shows in your dashboard. To disconnect any app, delete its MCP: <app> key under Developers → API keys. It stops on the next request. Access tokens last an hour and renew themselves; one left unused for 30 days expires.
For developers.
The server speaks streamable HTTP with OAuth 2.1 (PKCE, dynamic client registration) and exposes 303 tools, the same public API as our REST endpoints and the pocketsflow SDK.
Questions
Global or per project?
Either. ~/.cursor/mcp.json makes Pocketsflow available everywhere; .cursor/mcp.json keeps it to one project.
Can I keep it on test data?
Yes. Switch the dashboard to test mode before you click Allow access, and the agent works on sandbox data.
Do I need an API key?
No. You sign in to Pocketsflow and click Allow access, and the app gets a token for your account. API keys are only for headless servers and CI, where nobody can click Allow.
Can Cursor refund a buyer?
No. Payment refunds are issued from your dashboard. Cursor can find the order, check its payment and set the refund policy buyers see at checkout.
How do I disconnect Cursor?
Delete the MCP: Cursor key (the name the app gives itself) under Developers → API keys in your dashboard. Access stops on the next request.
Other AI apps.
Same server, same sign-in. Pick another app for its own setup.
Claude Codeclaude mcp addOne command in the terminal, then wire checkout and webhooks into your repo while it reads your store.- GitHub CopilotMCP: Add Server in VS CodeRun MCP: Add Server in VS Code and Copilot Chat can call your store while it edits your code.
- WindsurfCascade MCP configAdd the address to Cascade's MCP config and Cascade signs you in on its own.
Connect Cursor, then ask for your first product.
Free to start, no monthly fee. Your AI works in your account with the access you approve.
Start selling free