Skip to main content
One command:
1

Run the command

It registers a server named affixo in the project’s .gemini/settings.json. Add --scope user to put it in ~/.gemini/settings.json instead, so it’s available everywhere.
2

Sign in

Gemini CLI discovers that the server wants OAuth and opens a browser sign-in on first connect. Sign in with Affixo, then choose the workspace and the access level:
  • Read only — inspect campaigns, commissions, promoters and referrals.
  • Read & write — also create/update campaigns, set commission rules (including per-product rates), configure product commissions, and invite affiliates.
You must be an admin of the workspace to authorize a connector.
3

Check it loaded

Run /mcp inside Gemini CLI — affixo should be listed with its tools. Then ask: “List my Affixo campaigns.”

​
Adding it by hand

In .gemini/settings.json (or ~/.gemini/settings.json):
The key is httpUrl, not url. Gemini CLI reserves url for SSE endpoints, so a server written as url is dialled as SSE, fails to connect, and gives you no useful error. If gemini mcp add wrote url for you, change it by hand — some versions have had that bug.
Full tool catalogue and what each one can touch: MCP Server. Installing tracking with Gemini CLI instead? See Gemini CLI.