five steps to
your first report.

1 · sign in by email

Enter your email and we send a single-use sign-in link. It expires in 15 minutes. Signing in for the first time is the same step that creates your account.

Why: no password to set or remember. This email identity is also what you approve Claude against in step 3, so your keys and your agent stay tied to one account you control.

email me a sign-in link ▸

If that address is valid, a sign-in link is on its way from [email protected]. Check spam the first time — the domain is new. The link works once and expires in 15 minutes.

That did not go through. Check the address and try again; if it keeps failing, the sign-in service may be briefly unreachable.

2 · connect your networks

The emailed link opens your dashboard straight away — there is no token to copy or paste. Pick a network and a short guided form asks for exactly the keys it needs, with a note on where to find each one in that network's own dashboard. Save, and we run a live connection test so you can see it works before going further. Awin, CJ Affiliate, Impact, and Rakuten Advertising connect today — add them one at a time.

Why: your network API keys are entered here, in the encrypted dashboard, and nowhere else. They are never given to Claude or any MCP client — the agent only ever receives a scoped session (step 3). Holding them here is what lets the service run your reports while your machine is off.

open your dashboard ▸

3 · add it to claude

In Claude, add affiliate-mcp as a custom connector and sign in through your browser — again, no token to paste.

• →Claude Desktop or claude.ai: Settings → Connectors → Add custom connector, paste the transport URL below, then follow the browser sign-in and approve access.
• →Claude Code: run claude mcp add --transport http agentic-affiliate https://mcp.agenticaffiliate.ai/mcp, then /mcp and approve the browser sign-in.
• →Any other MCP client that supports remote servers with OAuth connects the same way, using the transport URL below.

https://mcp.agenticaffiliate.ai/mcp

Why: you approve access with the same email identity from step 1, and Claude receives a short-lived, scoped token — never your network keys.

4 · run your first report

Ask your agent something real:

• →“Show my unpaid commissions on Awin from the last 30 days.”
• →“Summarise last month's earnings across all my networks.”

Why: if that returns your data, the whole loop is working — keys in the dashboard, agent authorised by OAuth, reports on demand.

the honest bits

• →Four networks hosted today. Awin, CJ Affiliate, Impact, and Rakuten Advertising. Others stay local-only until their terms are checked — the free local server covers all of them.
• →Keys go in the dashboard, never in Claude. Credentials are entered only in the encrypted dashboard, decrypted only at the moment a request runs, and deleted with your account whenever you ask. Claude gets an OAuth session, not your keys.
• →Nothing sensitive is copied around. Sign-in is a one-time email link and Claude connects by browser OAuth — there is no session token to paste anywhere.
• →One long-lived token per network. These four networks only issue full-access API tokens, not scoped read-only ones. Generate one dedicated to this connection, and revoke it in the network's dashboard if you ever disconnect.
• →Local stays free and complete. Hosted removes the install and the laptop-awake constraint; it does not gate anything the open-source server already does.