Claude
- Open Customize › Connectors and choose Add custom connector.
- Paste the link, name it Affiliate1A if it asks, and choose Add.
- Choose Connect. Affiliate1A opens so you can sign in and allow it.
On a Team or Enterprise plan, an Owner adds it first under Organization settings › Connectors, then each person chooses Connect.
ChatGPT
- Open chatgpt.com/plugins, choose +, then Add custom MCP server.
- Name it Affiliate1A and paste the link under Connection.
- Choose I understand and want to continue, then Create as a plugin, and install it. Affiliate1A opens so you can sign in and allow it.
- In a new chat, type
@and pick Affiliate1A.
Your account and workspace settings decide whether you can add one.
Codex
- Add it:
codex mcp add affiliate1a --url https://affiliate1a.com/mcp - Sign in. Affiliate1A opens in your browser so you can allow it:
codex mcp login affiliate1a
The Codex app and IDE extension share this setup, or choose Add server in their settings.
Claude Code
- Add it:
claude mcp add --transport http affiliate1a https://affiliate1a.com/mcp - In Claude Code, run
/mcp, pick affiliate1a and choose Authenticate.
Other apps
- Add the link as a remote server that signs in through your browser.
Web apps other than Claude and ChatGPT also need the owner to turn on Allow other AI apps in Settings › Connected AI apps.
Signing in
- Affiliate1A opens in your browser. If you're signed out, type your brand handle and sign in.
- Check the app, the brand and what it can see, then choose Email me a code.
- Type the code from your email and choose Allow. You're back in your app, connected.
What it can do
See sales, creators, orders and payouts. Owners and admins can also let it suggest changes, which do nothing until you approve them in Affiliate1A.
It can never
- Record payouts or change bank details
- Change commissions, offers, codes or campaigns
- Change your team, password or sign-in
- Delete anything or see contact details
- Approve its own suggested changes
For AI agents
- The server is
https://affiliate1a.com/mcp: a remote MCP server over Streamable HTTP that answers with plain JSON. - Sign-in is OAuth 2.1 with PKCE (S256). Without a token the server answers 401, and its
WWW-Authenticateheader points tohttps://affiliate1a.com/.well-known/oauth-protected-resource/mcp. The authorization server's metadata is athttps://affiliate1a.com/.well-known/oauth-authorization-server. - Register with a Client ID Metadata Document or dynamic client registration. The scopes are
readandpropose;offline_accessis accepted for a refresh token. - A person has to finish sign-in in their own browser with a code from their email. Add the server, start sign-in, and ask them to complete it.
- Anything you prepare is a suggested change. It does nothing until the same person approves it in Affiliate1A, within 15 minutes, with a code from their email.
The same guide as markdown: affiliate1a.com/ai-apps.md