MCP server
Run your creator program from your editor.
Connect MyAppAffiliate to Claude Code or Cursor. Set attribution up by asking, then recruit, adjust, diagnose and pay, without opening a dashboard.
Works with any MCP client. Nothing to install.
A real session against our staging API, ids included.
Why it matters
Two things it does that a dashboard cannot.
Automation
Everything the dashboard does, without the dashboard.
"Pause any affiliate whose clicks are up 10× month-over-month but whose installs are flat."
Recruit forty creators from a CSV, mint each a link, change a rate, pause someone gaming clicks, run the monthly payout.
That is not a feature anyone ships. It is three queries and one write, exactly what an agent is good at.
Setup
The integration writes itself, then proves it works.
"Set up MyAppAffiliate in this repo."
Point your editor at your repo. It reads your stack, provisions your keys, writes the code into the right files, and hands you the one step it cannot do.
Then it verifies the whole chain against live data and tells you what is still broken.
Permissions
A tool you didn't grant doesn't exist.
Permissions aren't checked after the fact. Tools you haven't granted are never registered, so they never appear in the client's tool list. An agent cannot propose an action it cannot see.
Solid: reachable by a read + write keyDashed: never registered, so never offered
Money out
An agent cannot pay someone because it felt like it.
Payouts are irreversible, so they carry two locks: the permission above, and a confirmation that has to match the figures you were shown.
The payout has to quote back the figures from that preview. If a commission matured in between, it fails instead of paying a different number.
Workflows
Six things you can just ask for.
Your client shows these as commands. Each is a recipe over the same operations the dashboard uses, and one whose permissions you lack is never offered.
FAQ
The questions founders actually ask.
Which clients does it work with?
Anything that speaks MCP: Claude Code, Cursor, and the growing list of editors and desktop clients that have added support. It is a remote server, so there is nothing to install: one entry in your client config and a key.
Can an agent move my money?
Only if you let it. Paying out needs a permission that is never granted by default, so a key without it has no payout tool at all. The agent cannot see one, let alone call it. Even with it, a payout has to quote back the exact figures from a preview you approved, and if a commission matures in between the call fails instead of paying a different amount.
What stops a creator from tricking my agent?
Creator names, campaign names and webhook payloads are written by other people, and we treat them as data rather than instructions. No tool accepts an account id, so there is no parameter an injected instruction could widen to reach someone else's data, and every write is recorded with the key that made it.
Do I need to use an agent at all?
No. The dashboard does everything it always did. The MCP server is the same operations layer with a different front door, for people who already live in an editor.
What does it cost?
Setup tools and read access are on the free tier, because integrating in five minutes should not be gated. Writes come with Growth, and payouts with Scale.
Tell your editor to set it up.
One line in your MCP client config and a key. The free tier includes setup and read access, so the five-minute version costs nothing.