@gocushy/mcp
v0.13.0
Published
gocushy MCP server — let AI agents create checkouts, offers, and follow-ups that sell
Downloads
1,043
Maintainers
Readme
gocushy MCP server
Give any AI agent the tools to run a complete selling system: products, offers with order bumps and one-click upsells, hosted checkouts, subscriptions, coupons, embeds, orders, refunds, affiliates, email follow-up, and sales stats — on the merchant's own Stripe or PayPal account.
28 tools in all. Nothing is a mockup: the agent creates real checkouts that take real money into the merchant's own account. Totals, fees, and tax are computed server-side, so an agent can't ship a broken or mispriced checkout.
Install
npm install -g @gocushy/mcpPoint your client at the gocushy-mcp command (stdio transport), passing the
merchant's API key:
{
"mcpServers": {
"gocushy": {
"command": "gocushy-mcp",
"env": {
"GOCUSHY_API_KEY": "gc_your_key_here",
"GOCUSHY_API_URL": "https://api.gocushy.com"
}
}
}
}Or run it without installing — swap the command for
"command": "npx", "args": ["-y", "@gocushy/mcp"].
Then just talk: "Set up a checkout for my $49 course, add my $17 workbook as an order bump, and give me the embed code."
Create an API key at https://api.gocushy.com/signup.
Remote connection (ChatGPT and other hosted clients)
Prefer a URL over a local process? gocushy runs a hosted MCP endpoint. Put the merchant's key in the path:
https://gocushy-mcp.fly.dev/mcp/gc_your_key_hereFor ChatGPT connectors (which can't carry a key in the URL), connect to
https://gocushy-mcp.fly.dev/mcp and paste the API key on the consent screen —
the server speaks OAuth 2.0 (PKCE) for exactly this handoff.
Tools
A representative slice — 28 in total, spanning products, offers, checkout copy & layout, delivery, orders & sales, refunds, coupons, affiliates, email follow-up, webhooks, and business/tax settings:
| Tool | What it does |
|---|---|
| connect_payment | Start Stripe onboarding (returns a URL for the human — the one manual step) |
| connect_paypal | Connect a PayPal account as a payment rail |
| payment_status | Is the account ready to take payments? |
| create_product | Create a sellable product (one-time or subscription) |
| create_offer | Compose a checkout: product + optional bump + optional one-click upsell, plus a per-offer top logo (checkout_logo_url) |
| update_checkout | Customize checkout copy, layout, the brand banner, the per-offer logo, and the one-click upsell page (headline, body, accept/decline labels) |
| create_coupon | A promo code buyers type at checkout — works on one-time and subscription offers |
| get_checkout_link | Hosted checkout URL — works immediately |
| get_embed_code | Copy-paste overlay snippet for any site |
| list_orders / get_sales | Orders with bump/upsell flags; revenue and per-offer breakdown |
| refund_order | Full or partial refund (reverses the transfer + fee) |
| connect_email / set_followup | Wire buyers into the merchant's Mailchimp / ActiveCampaign sequences |
| create_affiliate / create_webhook | Affiliate links with holdback; order webhooks for custom fulfillment |
The full tool list, with every parameter, is advertised by the server itself — your agent discovers it on connect.
Design principles
- Server-side truth. Totals, fees, tax, and state live in the API; tools can't create a broken or mispriced checkout.
- Fail loudly. Validation errors come back verbatim so the agent can fix its call and retry.
- One human touchpoint. Everything is agent-operable except payment-provider KYC, which is legally the merchant's to complete.
Development
npm install && npm run build
GOCUSHY_API_KEY=gc_... node dist/index.js # stdio transport