API & MCP
Connect Claude, ChatGPT, Claude Code, Cursor, Codex, VS Code, Windsurf or Lovable to your Swazy. Your AI can build and edit products, run your link in bio, set up challenges and courses, look after your groups and draft your emails — with your OK, and never with your money.
Server URL
https://swazy.bio/api/mcp
Pick your app. Claude and ChatGPT sign in to Swazy — no token. Everything else can use a personal token from Settings → Connected AI apps.
claude mcp add --transport http --scope user swazy https://swazy.bio/api/mcpexport SWAZY_TOKEN="swz_pat_…" # your token from Settings → Connected AI apps
claude mcp add --transport http --scope user swazy https://swazy.bio/api/mcp \
--header "Authorization: Bearer $SWAZY_TOKEN"Each connection gets only the permissions you tick when you connect it. See and Make changes are on by default; your people and Swazy AI credits are off until you switch them on.
Your products, page, settings and sales numbers — no buyer details.
Buyers', members' and applicants' names and emails, orders, messages and bookings — and reply to them.
Edit your page, products, challenges, courses, groups and email drafts. It can't move money or send email blasts.
Start AI builds and edits that use your Swazy AI credits.
Your AI works through the same rules as Swazy's own buttons. You're responsible for what your connected apps do, under Swazy's Terms and Privacy Policy: no spam, no scraping other creators, nothing you couldn't do by hand.
Whatever app is connected, only you can:
Anything that reaches people or can't be undone comes back as a preview first — publishing your page, a price change on a live product, approvals, messages, removing a member, deleting a post. Your AI shows you and only goes ahead when you say so. Good apps also ask you before every change.
Up to 120 requests a minute per account. Each connection, per day:
Buyer and member details are only shared with connections you gave “See and contact your people”, and that AI company handles them under its own terms, at your direction. Words written by buyers and members are marked as data, so they can't give your AI orders. Swazy stores only a fingerprint of each token.
Settings → Connected AI apps lists every connection, its permissions, when it was last used and what it did. Revoke stops it within a minute. Tokens can expire by themselves, and every connection ends when you reset your password, change your account email or delete your account.
When your own AI writes a challenge, course or guide (create_program, create_guide), Swazy uses no credits. Asking Swazy AI to build or edit (build_product, edit_product) uses your credits like it does in Swazy — and never tops up your card on its own from a connected app.
The MCP server is Swazy's API: any HTTP client can call it with a token. Start with tools/list — every tool has a JSON Schema, a title and read-only / destructive hints.
A secure way for an AI app you already use to work in your Swazy workspace. MCP (Model Context Protocol) is the open standard Claude, ChatGPT, Cursor and Codex use to connect to tools; Swazy's lives at https://swazy.bio/api/mcp.
Claude (claude.ai and the desktop app), ChatGPT custom connectors, Claude Code, Cursor and Codex — and any app that connects to MCP servers over HTTP with sign-in (OAuth) or a bearer token.
Only when your AI asks Swazy AI to build or edit a product, and only if you gave it that permission. When your own AI writes a challenge, course or guide itself, Swazy uses no credits.
No. Bank details, plans, credits, refunds and sending email campaigns are only possible by you, in Swazy. Your AI can draft an email; you press Send.
Only if you switch on “See and contact your people” for that connection. What it reads then goes to that AI company under its own terms, at your direction.
Settings → Connected AI apps → Revoke. It stops working within a minute. Personal tokens can also expire by themselves after 30 days, 90 days or a year.
Make a free account, then connect the AI you already use.