Operate GoCushy with your AI

01 — Overview

What GoCushy is

GoCushy is an MCP-native checkout and funnel that an AI operates on the merchant's own Stripe account. Payments run as Stripe Connect direct charges: the money lands in the merchant's Stripe, the buyers are the merchant's customers, and GoCushy never holds funds and is never the merchant of record. Payouts run on the merchant's normal Stripe schedule, to their bank.

You (the agent) do the wiring: create the products, compose the offers, write the checkout copy, and hand back a live link. The one thing you cannot do is Stripe's identity verification — that returns a URL for the human to complete, and it is the only human step in the whole system.

02 — Setup

Connect it

Three ways in, one credential. Every connection is authenticated with the merchant's API key — it starts with gc_ and comes from the dashboard under Settings → API keys. Treat it like a password: anyone (human or agent) holding it can create offers, read sales, and issue refunds.

a. Local MCP — Claude Desktop, Claude Code, Cursor

The package is @gocushy/mcp on npm. For Claude Code, one command in the terminal:

claude mcp add gocushy -e GOCUSHY_API_KEY=gc_… -- npx -y @gocushy/mcp

For Claude Desktop (or Cursor's .cursor/mcp.json), add the server to the config file:

{
  "mcpServers": {
    "gocushy": {
      "command": "npx",
      "args": ["-y", "@gocushy/mcp"],
      "env": { "GOCUSHY_API_KEY": "gc_…" }
    }
  }
}

b. Remote MCP — ChatGPT & hosted agents

No install. For connector-style clients that can't send custom headers, put the key in the path — the key is the authentication, so set Authentication to None:

https://mcp.gocushy.com/mcp/gc_…

ChatGPT specifics: browser only, paid plan required. Turn on Developer mode under Settings → Security and login, then add the server from chatgpt.com/plugins with the + button.

c. REST API — anything else

The same surface, JSON in and JSON out. Base URL and bearer auth:

curl https://api.gocushy.com/api/v1/me \
  -H "Authorization: Bearer gc_…"

03 — The model

Mental model

Two nouns, one settlement. Keep them straight and the whole surface falls into place:

• Product — the thing being sold: a price plus delivery (where the buyer gets access). One-time or subscription.
• Offer — how it's sold: a product wrapped in a live checkout, with an optional order bump (a checkbox add-on on the page) and a one-click upsell (accepted after payment, card already saved).

product (price + delivery)
   └─ offer (live checkout + optional bump + upsell)
        └─ settles on the merchant's own Stripe

The same product can appear in many offers — standalone, as a bump on one checkout, as an upsell on another. Every paid order settles directly on the merchant's Stripe; GoCushy is only ever the machinery in between.

04 — The happy path

Golden path

Zero to a shareable checkout link in six moves. Check state first, do the one human handoff, then build:

1. payment_status

   Check whether the merchant's Stripe is connected and charges are enabled. If it already is, skip straight to create_product.

2. connect_payment — the human step

   If Stripe isn't ready, this returns the hosted onboarding URL. Hand it to the human to open and complete Stripe's identity verification. You cannot do this part; nothing else needs a human.

3. create_product

   Create the thing being sold — a price (in cents) and delivery (see below). Subscriptions also need an interval.

4. create_offer

   Wrap the product in a checkout. Attach an order bump and one-click upsell if you have them. The offer goes live immediately.

5. get_checkout_link

   Fetch the hosted checkout URL (and its short gocushy.com/l/… link). This link is the preview — open it to see exactly what buyers see.

6. Share

   Hand the link back to the human to drop into emails, posts, or their AI-built page. Done.

05 — Deliver the goods

Delivery

A live offer has to actually give the buyer something. Before you share a link, make sure the offer can deliver — set at least one of these:

• delivery_url — the members area, download, or booking link. It becomes the "Access your purchase" button on the receipt and the signed thank-you page.
• delivery_note — on-screen access text shown with (or in place of) the button: instructions, a code, next steps.
• An order.paid webhook — register one with create_webhook so the merchant's own system grants access when the order is paid.

06 — What you can't do

Guardrails

Some things are deliberately out of your reach. These aren't missing features — they're what lets a merchant safely hand an agent their API key.

• Prices, totals, and countdowns are computed server-side. You can't ship a checkout that charges a different amount than it shows, and you can't fake scarcity — a deadline must be a real future date, and the countdown hides when it passes and can never reset per-visitor.
• Checkout copy is whitelisted blocks. Headline, subheadline, bullets, testimonials, guarantee, deadline, image, button text, accent — plain text, length-capped, HTML-escaped into fixed zones. You can fully customise a checkout and structurally cannot break the layout or hide the order form.
• Buyer-sensitive URLs are signed. The thank-you page and access links only render for genuinely paid orders — nobody reaches the product by guessing a URL.
• Tax and affiliates are gated behind the Tax & Affiliates Pack. Real tax collection, compliant invoices, and the affiliate program unlock with the add-on.
• Every action is logged. A full activity trail records who did what — the merchant, an agent (tagged with its API key), or GoCushy itself. Nothing an agent does is invisible.

07 — Reference

The tools

Everything you can do, grouped. You rarely name these to the human — they describe what they want, you pick the tools — but here's the full map.

08 — In practice

Recipes

What the human actually says, and roughly what you do. They speak in sentences; you translate into the tools above.

"Set up a NZ$49 course with a NZ$19 workbook bump and add buyers to my welcome email."

create_product (course, 4900) → create_product (workbook, 1900) → create_offer with the workbook as the bump → connect_email if needed → set_followup on the purchase trigger → get_checkout_link and share.

"Run a 48-hour 20%-off coupon."

create_coupon for 20% off the offer, then hand back the code. The checkout applies the discount server-side; the countdown, if you set one, stays honest.

"Refund order #1042."

Confirm the order and amount with the human, then refund_order. The refund goes back through the merchant's Stripe and cascades — invoice, any refund follow-up rule, and any affiliate commission clawback all stay consistent.

"How did last month go, and who are my best affiliates?"

get_sales for the revenue, order counts, and per-offer breakdown → list_affiliates for each affiliate's numbers and due balance. Summarise it in plain English.

09 — Pricing & access

Pricing & access

One plan, billed monthly in New Zealand dollars:

NZ$99 a month including GST (NZ$86.09 + GST), or NZ$950 a year paid annually. Everything is included — there is no feature tier, no per-seat charge and no upgrade to unlock tax, invoices or affiliates. The first 30 days are free.