Add a referral program with your AI tools
Add a referral program with the AI tool you already use. Each guide gives you the prompts or the rules file, shows where the signup call goes, and records what we actually ran.
Coding agents
Connect the RefRef MCP server for configuration, and add a rules file so that the agent writes the tracking code the right way.
AI app builders
For apps that you build in a browser. Each guide follows the builder's real stack: where accounts live, where server code runs, and where the key is kept.
01Does the MCP server add referral tracking to my app?
No. MCP reads your RefRef configuration and prepares changes that a person approves in the Console. Tracking is code in your app: the landing script in the browser, and a signup call from your backend when an account is created. The rules file tells the agent how to write that code.
02Where does the RefRef API key go?
Only in server-side secret storage that the browser never sees, as REFREF_API_KEY: never in browser code, a public environment variable, a prompt, or a commit. The landing script in the browser needs no key, and the MCP connection uses your Console sign-in through OAuth, not the API key.
03Does the referral work in a preview deployment?
Test it on the published app at its final domain. The referral cookie belongs to the domain where the referral link lands, and preview addresses differ from production.
04Can the agent change my live referral program by itself?
No. Every MCP change is a proposal. An owner or admin of the Workspace approves it in the Console, and the agent can apply only the approved proposal. Start in a Sandbox Project.
One contract under every tool
The landing script captures the referral click in the browser. Your backend sends one signup, with the browser's handle, when it creates the account. MCP helps an agent read and configure RefRef; it does not install tracking.