Your checkout, one command away in Claude Code.
Add Swipefast to Claude Code once. Ask about your numbers without leaving the terminal, or have Claude build a checkout and design its sales page while you work.
Build a checkout for my course at $197, with a $47 upsell.
Done. It’s a draft, so nothing is live yet. Open it in Swipefast to check the page, then press Publish when you’re happy.
Set up Claude Code in a few minutes.
- 1Add the server
Open Terminal (your normal prompt, not inside Claude Code) and paste the first command. It adds Swipefast for every project.
- 2Sign in
Start Claude Code with claude, type /mcp, pick swipefast and choose to sign in. Swipefast opens in your browser: sign in and press Allow.
- 3Or use your key
Rather paste a key? Use the second command instead. In Swipefast, Settings, Your connection key has a Copy Claude Code command button with your key already in it.
- 4Ask, or build
Ask in plain words. To build a checkout, type /mcp__swipefast__setup_checkout and say what you sell. Claude asks for the price and delivery link and creates a draft for you to publish.
claude mcp add --scope user --transport http swipefast https://swipefast.io/api/mcpclaude mcp add --scope user --transport http swipefast https://swipefast.io/api/mcp \
--header "Authorization: Bearer sf_live_your_key_here"https://swipefast.io/api/mcpEvery app connects to this one address. The MCP docs list every tool and how sign-in works.
Ask for the answer, not the export.
“List my Swipefast checkouts and their conversion rates.”
“Build a checkout for my course at $197, with a $47 upsell.”
“Design a sales page for The Offer Maker in my brand colours.”
“Which coupons were used this month, and how much did they cost me?”
Claude Code drafts. You approve.
Changes to a draft happen straight away. A change to a live checkout waits for your OK on the Approvals page, and you get an email about it. Requests expire after 7 days, and anything you approve can be rolled back.
Revenue, orders, customers, traffic, products, coupons and how each checkout is doing.
Draft checkouts, order bumps, upsells, sales pages and coupons. Live changes wait for you.
No refunds, no payouts, no publishing. Those stay with you in the dashboard.
Every tool is tied to the account that connected it. No prompt can point one at somebody else's.
The short answers.
Should I sign in or use my key?
Signing in is simpler and you can disconnect it from Settings on its own. A key is handy for scripts and servers; it's the same key the REST API uses.
Can it change a checkout people are buying from?
It can ask to. Changes to a draft happen straight away. A change to a live checkout, like a new price or a new upsell, waits on the Approvals page until you approve it, and you get an email. You can roll back anything you approved.
Can it refund orders or move money?
No. The tools read your numbers, make coupons and build or change checkouts. Refunds, payouts and publishing stay with you in the dashboard.
Does connecting an AI cost extra?
No. The MCP server is included in every Swipefast plan. Your AI app's own plan is separate.
How do I disconnect it?
Apps you signed in to are listed in Settings, under Connected apps, each with its own Disconnect button. If you used your API key, rotate it in Settings and every connection using the old one stops at once.
Your checkout, run from the chat you already have open.
One plan with everything in it, the AI connection included. Try it for 30 days, with a full refund if it’s not for you.