Model Context Protocol
Your checkout data,
inside your AI.
Connect Swipefast to Claude, ChatGPT, or any MCP client and ask about your sales in plain language. No dashboard, no SQL, no export. Sign in to Swipefast from the app, or paste the API key you already have.
- “How much did I make last month, and how does that compare to the month before?”
- “Which checkout converts best, and where is that traffic coming from?”
- “Who are my top 10 customers and what have they spent?”
- “Make me a 25% off code for Black Friday, capped at 100 uses.”
Connect it
The server is version 1.35.0 (see what changed) and speaks MCP 2025-06-18 over HTTP at https://swipefast.io/api/mcp. Connect by signing in (OAuth), or with your API key from Settings.
Add a custom connector with the address https://swipefast.io/api/mcp and no key. The app opens Swipefast, you sign in and press Allow, and it’s connected. In Claude it’s under Customize → Connectors; in ChatGPT it’s Plugins → Add custom MCP server (paid plans, Plus included). Setup for every app we’ve checked is on /agents. On the Allow screen you can untick building and changing checkouts to give the app read-only access. Connected apps are listed in Settings, each with its own Disconnect button.
claude mcp add --scope user --transport http swipefast https://swipefast.io/api/mcp \ --header "Authorization: Bearer sf_live_your_key_here"
{
"mcpServers": {
"swipefast": {
"type": "http",
"url": "https://swipefast.io/api/mcp",
"headers": {
"Authorization": "Bearer sf_live_your_key_here"
}
}
}
}OAuth 2.1 as the MCP spec describes it. An unauthenticated request gets a 401 whose WWW-Authenticate header points at /.well-known/oauth-protected-resource, which names this site as the authorization server (/.well-known/oauth-authorization-server). Clients register themselves (RFC 7591), and PKCE with S256 is required. Scopes are read and write. Access tokens last an hour; refresh tokens rotate, and reusing an old one disconnects the app. Tokens only open this endpoint, never the REST API.
To check the endpoint is reachable before wiring up a client, a plain GET returns the server card:
curl https://swipefast.io/api/mcp
What it can do
37 read-only tools and 27 that write. Every tool is scoped to your account by construction — none of them takes a user id, so there is no way to point one at somebody else’s data.
list_productsreadget_productreadcheckout_qr_codereadlist_ordersreadrevenue_summaryreadrevenue_by_monthreadtop_customersreadlist_accountsreadaccount_summaryreadtraffic_sourcesreadsubscription_healthreadrevenue_forecastreadcompare_checkoutsreadaffiliate_dashboard_linkreadlist_couponsreadcoupon_statsreadcreate_couponwritesget_sales_page_guidereadget_brand_guidereadset_brand_guidewritesget_link_pagereadset_link_pagewritessetup_checkoutwritesadd_order_bumpwritesadd_upsellwritesset_sales_pagewritesget_sales_pagereadedit_sales_pagewritesroast_sales_pagereadcheck_postreadupdate_checkoutwritesupdate_order_bumpwritesupdate_upsellwritesupdate_price_optionwritesremove_order_bumpwritesremove_upsellwritesset_offer_chainwritesapproval_statusreadpublish_checkoutwriteslist_coursesreadadd_lessonwriteslist_coaching_clientsreadadd_coaching_clientswriteslist_findingsreadresolve_findingwriteslist_rulesreadcreate_rulewriteslist_email_optionsreadlist_email_rulesreadadd_email_rulewritesremove_email_rulewritesoffer_statsreadbuyer_journeyreadtop_pagesreadfunnel_statsreadtracking_statusreadinstall_trackingwritesset_retention_offerswritesretention_offer_statsreadchange_subscription_planwritesaffiliate_payoutsreadjv_statementreadcreate_payout_runwritesset_commission_tierswritesWorth knowing
Money comes back twice. Every amount is returned as cents and as a formatted string, because a model reading a bare 9900 will cheerfully tell you that you made ninety-nine hundred dollars.
The numbers match your dashboard. Test orders are excluded and refunds are handled the same way the dashboard handles them — the tools call the same functions the dashboard does, so the two can never disagree.
What the writing tools can do. create_coupon makes a discount code. set_brand_guide saves the seller’s brand guide, an account setting buyers never see, so it applies straight away and changes no existing checkout. setup_checkout creates a checkout as a draft, and update_checkout and the tools beside it change any checkout through the same rules as the dashboard editor. Drafts change straight away. On a live checkout, words, design, pages and switching, removing or reordering offers change straight away too and appear in Dashboard → Approvals, where the seller can roll them back. Anything that touches money (a price, a delivery link, a new offer, a plan) changes nothing: the call returns status: "pending_approval", a request id and an approval link, and the seller is emailed. Only a signed-in seller can approve, in Dashboard → Approvals; no key or tool can. A snapshot is taken before any change on a live checkout, so it can be rolled back. Requests expire after 7 days, and approval_status tells the model what happened. offer_stats gives one checkout’s visits, conversion, bump and upsell take rates, average order and refunds. Errors come back as {code, message, hint}. Nothing here can publish by itself, unpublish, refund or move money: publish_checkout only files a request, which the seller confirms in Swipefast, and a yes in the chat doesn’t count. Everything else is annotated read-only so clients can auto-approve it.
Courses go through the same door. list_courses reads the seller’s Hub courses and their outline, and add_lesson adds a lesson (a title, Markdown text and an optional video link) to a module. On a draft course it applies straight away. On a live course it applies straight away too and appears in Approvals, and rolling it back removes just that lesson.
Rules watch the numbers for you. create_rule sets a performance rule on a checkout: when its conversion, order bump or upsell take rate, or refund rate crosses a line, Swipefast either files an approval request (switch an offer, change a price or wording) or leaves a finding. list_findings reads those, so the model can look at the checkout, propose one change and mark the finding done with resolve_finding.
Set up a checkout in one go. In Claude Code, type /mcp__swipefast__setup_checkout and say what you sell. Claude asks for the price and delivery link, builds the checkout (with an order bump, upsell and sales page if you want them) as a draft, and gives you the link to preview and publish.
Pages follow the same rules as the blog prompt. Before writing a sales page, the agent calls get_sales_page_guide, the same brief as our Claude and Codex guide, so the page stays scoped, phone-friendly and points every button at the checkout. For an existing checkout, type /mcp__swipefast__design_sales_page.
From the terminal, or as an agent skill. The open-source swipefast CLI calls these same tools with your key (swipefast products, swipefast stats, swipefast call <tool>), and its agent skill teaches Claude Code and other agents the rules: never invent a price, money changes on a live checkout wait for approval, publishing is the seller’s call.
Your key is your key. It is the same one the REST API uses. Rotating it in Settings disconnects every client that uses the key. Apps you signed in to are separate: disconnect them under Connected apps.
What changed
You approve this server once, and from then on your AI trusts what its tools say they do. So the tools never change quietly: every change to what your AI can see or do gets a new version number (clients see it as serverInfo.version) and an entry here. When a change lets your AI do something it couldn’t before, we email everyone who has connected one. Don’t want it? Disconnect the app or rotate your key in Settings and it loses access at once.
1.35.010 November 2026- update_checkout's campaign takes countdownBanner: a bar across the top of the checkout counting down to closesAt, with the seller's text before the time left ("" for the default "This offer ends in"). It needs closesAt. Every buyer sees the same real deadline.
- campaign also takes endedTitle and endedMessage: what the checkout says once it has closed, instead of the default.
- get_product's campaign shows countdownBanner, endedTitle and endedMessage.
1.34.09 November 2026- add_email_rule takes when: checkout_abandoned, with wait_hours (1, 3, 12, 24 or 48, default 24): someone typed their email on the checkout and still hadn't paid that many hours later, so add them to a tag or sequence in the seller's email tool. It runs once per person and checkout, skips anyone who bought in the meantime, and never runs in test mode or on the free trial.
- list_email_rules shows those rules with their waitHours.
1.33.05 November 2026- setup_checkout and update_checkout take booking.package: how many calls each client gets (in total, each month, or no limit), how many they can book ahead, until when they can move or cancel, and whether buyers pick their first call at checkout. A subscription can now sell a monthly package; leaving package out keeps the one set.
- list_coaching_clients: a package's clients, with calls booked, calls left and calls to come, plus the Hub address.
- add_coaching_clients: add clients by email (people who pay another way, or not at all), optionally emailing each one a link to book.
1.32.04 November 2026- setup_checkout and update_checkout take intake: up to 5 questions buyers answer in the checkout before paying (short answer, long answer, link, checkboxes or one choice), each optional or required. On update_checkout the list replaces the questions, and null or [] removes them. Any checkout, every plan.
- Questions change no prices, so on a live checkout they apply straight away (status applied; the seller can roll it back). get_product shows them, and list_orders shows each order's answers.
1.31.04 November 2026- setup_checkout and update_checkout take booking: call length, how often a call can start, a buffer, minimum notice, how far ahead people can book, the seller's time zone, their weekly hours and whether to show spots left. On update_checkout it replaces the rules and null turns booking off. One-time prices and payment plans only.
- Booking changes no prices, so on a live checkout it applies straight away (status applied; the seller can roll it back). get_product shows the booking rules. Only for sellers who have calendar booking.
1.30.04 November 2026- get_link_page reads your link in bio page (your store address /links): what's on it, whether it's published, and the checkouts you could show.
- set_link_page changes it: name, bio, photo, social profiles, links and which checkouts it shows, in order. Links must be https:// or mailto:. It can't publish or unpublish the page, or show your revenue on it: you switch those in Swipefast. On a published page, changes show straight away.
1.29.030 October 2026- list_accounts lists your own account and every client account whose team you're on, with your role in each. It's only offered to people on more than one account.
- For them, every tool takes an optional `account` (an id from list_accounts). Left out, the call is in your own account as before; nothing carries over from one call to the next. Your role on that team decides what the call can do, checked on every call, and live checkouts follow that account's approvals.
- Each answer then starts with the name of the account it came from.
1.28.029 October 2026- list_email_options, add_email_rule and remove_email_rule work with a connected MailCheap newsletter: a rule adds the buyer to the newsletter (kind publication), or to it with one of its tags, when they buy, add an order bump or take an upsell.
1.27.028 October 2026- On a live checkout, update_order_bump, update_upsell and update_price_option with active (switching it on or off), remove_order_bump, remove_upsell and set_offer_chain apply straight away (status applied), listed on your Approvals page with a roll back. Rolling back a removed offer brings it back with its place in the chain.
- set_retention_offers applies straight away when it only switches the offers on or off or changes their message; a discount or a pause still waits for your approval.
- Still waiting for your approval: prices, currency, billing, delivery links, payment plans, early-bird prices and campaigns, a new order bump or upsell, retention discounts and pauses, plan changes, publishing and payouts.
1.26.028 October 2026- On a live checkout, set_sales_page, edit_sales_page, and the words and design in update_checkout, update_order_bump, update_upsell and update_price_option apply straight away (status applied). Each one is listed on your Approvals page, where you can roll it back.
- Anything about money still waits for your approval: prices, currency, billing, delivery links, payment plans, early-bird prices and campaigns, switching an offer or price option on or off, adding, removing or reordering offers, retention offers, plan changes, publishing and affiliate payouts.
- add_lesson puts a lesson into a live course straight away too, with a roll back.
1.25.028 October 2026- list_email_options, add_email_rule and remove_email_rule work with a connected HighLevel sub-account: a rule adds the buyer to one of its tags, or starts one of its published workflows (kind automation), when they buy, add an order bump or take an upsell.
1.24.028 October 2026- New tool update_price_option changes one price option (Standard, VIP and so on): its name, the line under it, its price, or takes it off the checkout. On a live checkout it waits for your approval, like every other change, and you can roll it back. Subscribers already on an option keep the price they signed up at.
- get_product now shows each price option's description.
1.23.228 October 2026- create_coupon switches on the code box (Accept discount codes) on the draft checkouts the code covers, and returns codeBox: the checkouts switched on, and any live ones still without a box for you to turn on in Swipefast (Discounts lists them with a Turn on button). Live checkouts are never changed without you.
1.23.125 October 2026- list_findings also returns nextSteps: the one change Pip recommends for each of your busiest live checkouts (add or rewrite a bump or upsell, fix the sales page, a payment-step drop, a phone-only problem), with the numbers behind it. Read-only; nothing else changed.
1.23.025 October 2026- traffic_sources also returns visitorSources: people by channel (search, social, AI assistants, email, paid, referral, direct) and by source, with the revenue each brought and revenue per visitor.
- New read-only tools: buyer_journey (one buyer's path from the post that found them to the upsell they took), top_pages (pages people read and what those readers spent), funnel_stats (where buyers drop off on a checkout or one of your funnels) and tracking_status (whether tracking is reporting).
- New tool install_tracking adds your own website to visitor tracking (Starter 1, Pro up to 10) and returns the tag and a prompt your coding AI can use to install it. It changes nothing on your checkouts.
1.22.321 October 2026- The server instructions say sellers may call Swipefast "swipe fast" or "Pip", its penguin mascot, so "ask Pip what sold this week" reaches these tools. No tool changed.
1.22.221 October 2026- set_brand_guide, set_sales_page, edit_sales_page, update_checkout, update_order_bump, update_upsell, set_offer_chain, set_retention_offers and set_commission_tiers are annotated destructiveHint: true, since each overwrites what was there. They run, or ask for your approval, exactly as before.
1.22.121 October 2026- remove_order_bump, remove_upsell, remove_email_rule, change_subscription_plan and create_payout_run are annotated destructiveHint: true. Nothing else changed: they run, or ask for your approval, exactly as before.
1.22.020 October 2026- check_post returns the sell score only when you pass productId or sell: true (it's null otherwise), so a story or tips post isn't marked down for not selling. The slop score always comes back.
- A link in the post or a plain way to buy (DM me, link in my profile, book a call) passes the sell check; "link in the comments" or "in the replies" doesn't, since LinkedIn holds those posts back too.
1.21.020 October 2026- get_sales_page, set_sales_page, edit_sales_page and roast_sales_page now answer with slop: a 0-100 score for the page's words and up to 8 flags, each with the exact phrase. Same plain rules as Post check: no AI, nothing stored. When the score is 20 or more, your AI fixes the flagged phrases, keeps the facts, and saves again. On a live checkout the score is of the page waiting for your approval, and fixes still wait for your approval.
- get_sales_page_guide has a "Write like a person" section built from the same rules (no reframes, buzzwords, dead openings, engagement bait or em dashes; plain words, specifics, contractions), so the page comes out clean the first time.
1.20.020 October 2026- check_post: your AI scores a LinkedIn, X, Threads or Substack post you're about to publish: a slop score with the exact words that read like filler, and a sell score (a hook, the offer, a reason to click, a link, a real result, the length). Name the checkout and it also checks the post mentions it and states its real price. Plain rules, no AI and nothing stored. It only reads.
1.19.016 October 2026- set_offer_chain: your AI sets the order of the one-click offers buyers see after paying, and where each yes and each no leads: another offer or the thank-you page. Up to 5 offers, on every plan (a downsell is the offer a no leads to). On a live checkout it waits for your approval, like any other change.
- add_upsell can now put a new offer in the chain: after another offer, when the buyer says yes or no (a downsell is an offer after the upsell, on a no). On a checkout that already has an offer after payment it asks where, instead of adding one buyers never see.
- get_product shows the chain (offerChain), and offer_stats shows each offer's views, takes, take rate and revenue, and the paths buyers took ("took offer 1 then offer 2").
- Buyers are only ever charged for an offer they say yes to, the way their first payment allows: added to the same card, a fresh card payment after pay later or crypto, or a PayPal approval.
1.18.016 October 2026- affiliate_payouts: what you owe each affiliate and JV partner (cleared to pay, on hold, on its way in a PayPal payout, and paid), how each one is paid, the payouts already sent and how they're doing, and your commission tiers and recurring commission. It only reads.
- jv_statement: a JV partner's revenue split for a month (each payment, the rate, their share, refunds taken out), or every partner with their split and balance. It only reads.
- create_payout_run: your AI asks you to pay what's cleared, with one PayPal payout from your own PayPal (Pro) or by recording that you paid another way. It never pays by itself: it always waits for your approval in Swipefast, and pays only what had cleared when it asked. A PayPal payment counts as paid only once PayPal confirms it.
- set_commission_tiers: your AI sets commission tiers (a higher rate after a number of sales or an amount of revenue in a month), recurring commission on renewals, and the affiliates' leaderboard (Pro). Once your program has an approved affiliate, it waits for your approval like any other change.
1.17.016 October 2026- On an account with a team (Pro), each AI connection and API key belongs to the member who made it, and acts with their role: Owner, Admin, Editor, Support or Viewer. An Editor's AI builds and changes checkouts, coupons, courses and rules but can't change a subscriber's plan; a Support member's AI can change plans but not checkouts; a Viewer's AI only reads.
- Your AI only sees the tools its role can use. A tool outside the role answers with a new error, insufficient_role, and the instructions now tell your AI to tell you rather than retry.
- The role is checked on every call, so changing someone's role limits their AI straight away, and removing them disconnects it. Changes waiting on Approvals record which member asked and which member approved.
- Nothing changes for an account without a team: its owner's AI can do everything it could before.
1.16.016 October 2026- change_subscription_plan: your AI moves one subscriber to another of a checkout's price tiers (Pro). An upgrade starts now and charges the difference for the rest of their period on the card they pay with; a downgrade starts at their next payment, with no refund. It can also call off a downgrade that's waiting. On a live checkout, and whenever it would charge real money, it waits for your approval: it never charges without it.
- get_product now lists a checkout's price tiers, and for a subscription whether subscribers can change plans themselves.
- list_orders: each order now says how the buyer paid: card, PayPal, Lemon Squeezy, or by name for buy now, pay later (Klarna, Afterpay, Affirm) and stablecoins (USDC).
- account_summary: also says whether buy now, pay later and stablecoin payments are switched on for your checkouts. It only reads: you switch them in Integrations, Stripe.
1.15.016 October 2026- subscription_health: subscriber churn, revenue churn, net revenue retention, average lifetime and lifetime value, with active subscribers and MRR, plus each month's cancellations and who ended them (the buyer, a failed card, or other). Your AI can answer why churn went up. It only reads.
- revenue_forecast: an estimate of the revenue already on the way over the next 3, 6 and 12 months, from renewing subscriptions and payment plan instalments still to come. It says when a part can't be worked out.
- compare_checkouts: two to four checkouts side by side over a window: visits, orders, conversion, order bump and upsell take rates, average order, revenue and refunds.
- coupon_stats: each discount code's uses, revenue, discount given and average order over a window.
- checkout_qr_code: your AI makes a QR code for a checkout's buyer link, as an SVG, for a flyer, a slide or an event. Give it a tag (qr, event, workshop) and sales from the code show that tag in Sales and Reports. It changes nothing. QR codes are part of Pro; on Starter your AI gets an upgrade message instead.
- set_retention_offers: your AI sets what a subscriber is offered at their cancel link, before the cancel goes through: a percentage off their next few payments, a pause of a few months, or both, with your own message. Each subscriber sees it once. On a live checkout it waits for your approval, like any other change.
- retention_offer_stats: how many subscribers saw the offer, how many stayed, by discount or pause, and the monthly revenue kept.
- affiliate_dashboard_link: the private link to one affiliate's dashboard (their links, clicks, sales and commission, with no buyer details), found by id, code, email or name, and whether affiliates get an email when they earn a commission. It changes nothing.
1.14.014 October 2026- get_brand_guide and set_brand_guide: your AI reads your brand guide (colours, fonts, tone of voice, words to use and avoid) before it drafts copy or a page, and can save one for you, including importing a brand.md from your files. It's an account setting buyers never see. New checkouts take their colour, font and theme from it; existing ones don't change.
- get_sales_page_guide opens with your brand guide when you have one, and the setup and design prompts tell your AI to read it first.
- roast_sales_page and the roast_my_page prompt: Pip reviews the page above a checkout, 5 to 8 specific points, each with its fix. It changes nothing; your AI asks which fixes you want and applies them with edit_sales_page, so a live checkout still waits for your approval.
1.13.014 October 2026- get_sales_page_guide takes a style (modern, classy, jacob, bold, minimal or playful) and lists them, so your AI can offer you a look before it designs the page.
- Once your page is live, your AI may mention, once, that you can share it and tag @getswipefast for a reshare.
1.12.014 October 2026- get_sales_page returns the HTML of a checkout's sales page, or of an upsell's own page, so you change what's there instead of rewriting it from memory.
- edit_sales_page changes part of either page with find-and-replace edits, all or nothing. On a live checkout it waits for the seller's approval, like any other change.
1.11.013 October 2026- setup_checkout and update_checkout take a price of 0 for a one-time checkout. Buyers get it with their name and email, no card. A paid order bump makes the order paid as usual; a paid upsell is offered after the free order and paid for on the offer screen. Subscriptions still need a price above zero.
1.10.013 October 2026- update_checkout takes campaign: how many seats, when the checkout opens and closes (with a time zone), and where a closed checkout sends people. Buyers see seats left and a countdown; the checkout closes on its own when it sells out or time runs out. On a live checkout it waits for the seller's approval, like any other change.
- get_product shows the campaign: whether it's upcoming, open or closed, and the seats left.
1.9.011 October 2026- list_email_options, add_email_rule and remove_email_rule work with a connected Kajabi account: a rule adds the buyer to one of the seller's Kajabi tags when they buy, add an order bump or take an upsell. The tag can start a Kajabi sequence or automation.
1.8.010 October 2026- add_email_rule: when someone buys a checkout, adds its order bump, takes its upsell, is refunded or cancels, add them to a tag or sequence (or automation, publication or group) in the seller's connected email tool. With several order bumps or upsells it can be for one. It applies straight away; the seller can pause or remove it.
- list_email_options: the tags and sequences in each connected email tool. list_email_rules and remove_email_rule: read and remove the seller's automation rules.
1.7.010 October 2026- setup_checkout and update_checkout take paymentPlans: ways to pay in instalments beside paying in full, e.g. 4 weekly payments of $50. Each plan has a number of payments, the amount of each and how often (every week or every month). One-time card checkouts only. On update_checkout the list replaces the old one and [] removes them; on a live checkout it's an approval request, and rolling it back restores the old plans.
- get_product lists the checkout's payment plans.
1.6.09 October 2026- publish_checkout: ask the seller to publish a draft checkout. It never publishes by itself: it files a request the seller confirms with one tap in Swipefast, and a yes in the chat doesn't count. Anything that would stop the checkout going live is reported first. Rolling an approved publish back makes it a draft again.
1.5.09 October 2026- list_courses: the seller's Hub courses, each with its status, students and outline (module ids and lesson titles).
- add_lesson: add a lesson (title, Markdown text, optional video link) to a module, a new module or the last one. On a draft course it applies straight away. On a live course it files a request on the seller's Approvals page, and rolling it back removes just that lesson.
1.4.09 October 2026- create_rule and list_rules: watch a checkout's conversion, order bump or upsell take rate, or refund rate every day, and act when it crosses a line. A fixed action (switch an offer on or off, set a price, change wording) files a request on the seller's Approvals page; it never changes a live checkout by itself.
- list_findings and resolve_finding: rules set to "flag it for my AI" leave findings. Read them, propose one change through the edit tools, then mark them done.
1.3.08 October 2026- update_checkout's language now takes fr (French) and de (German) as well as en and es. It sets the checkout, upsell, thank-you page, buyer emails and course Hub.
1.2.08 October 2026- On a live checkout, update_checkout, set_sales_page and the order bump and upsell tools no longer change anything straight away. They send you an approval request (by email and in Swipefast), and nothing reaches buyers until you approve it.
- Drafts still change straight away.
- Every approved change can be rolled back in one click, back to exactly how the checkout was.
- Requests you don't decide on expire after 7 days. Your AI can't approve them.
- New approval_status tool: your AI can check whether you approved, rejected or rolled back a change.
- New offer_stats tool: visits, conversion, order bump and upsell take rates, average order and refunds for one checkout.
- Errors now come back with a code and a hint, so your AI knows what to do next.
1.1.04 October 2026- New update_checkout tool: change a checkout's name, price, billing, delivery, thank-you page and the rest, draft or live.
- New update_order_bump, update_upsell, remove_order_bump and remove_upsell tools.
- add_order_bump, add_upsell and set_sales_page now work on live checkouts, not only drafts.
- get_product returns everything you can edit, so the AI changes what is there rather than guessing.
- On a live checkout the AI is told to confirm any price, currency, billing or delivery change with you first, and every change comes back as a before-and-after list.
- Still not possible: publishing, unpublishing, refunds or moving money.
1.0.05 September 2026- Read-only tools for checkouts, orders, revenue, customers and traffic.
- create_coupon to make discount codes.
- Added on 28 September under the same version number: setup_checkout, add_order_bump, add_upsell, set_sales_page, get_sales_page_guide and the two prompts, all limited to drafts. Changes like that now always get their own version.