Skip to Content
DocumentationAffiliate programConnect your AI assistant

Connect your affiliate AI assistant

The affiliate MCP server lets a compatible assistant read your account, retrieve the media kit and perform supported account actions when you instruct it. It is an account service at https://affiliates.keepkey.com/api/mcp, using Streamable HTTP and a Bearer API key.

This is separate from BEX Agent Mode, which connects a browser through KeepKey Desktop, and from the dropship REST API.

Connect

Episode AFF 06 · Connect your AI assistant · 1:57 · KeepKey, step by step
  1. Complete your approved affiliate profile, then open Agent setup in the portal.
  2. Read the API-key controls. Copy agent prompt includes your private key and connection details. If an active key exists but is not available in this visit, copying a new prompt replaces that key and disconnects clients using the previous one.
  3. Paste the prompt into your intended assistant privately. Allow it to configure an HTTP MCP server with the endpoint and Authorization header. Follow that client’s reconnect step if needed.
  4. Ask it to discover the available tools and call get_profile.
  5. Compare the returned affiliate identity and code with the portal. A saved server entry or a copied prompt is not proof of a working connection; a successful account tool response is the check.

For manual configuration, a client supporting this JSON format uses the following shape. Replace the placeholder privately in your client’s configuration; do not commit it:

{ "mcpServers": { "keepkey-affiliates": { "type": "http", "url": "https://affiliates.keepkey.com/api/mcp", "headers": { "Authorization": "Bearer YOUR_PRIVATE_AFFILIATE_KEY" } } } }

Configuration locations and secret storage differ by client. Use its official MCP documentation; Claude Code’s MCP guide  documents HTTP connections and headers. A client that only supports an OAuth connector may not support this Bearer-key configuration.

Know what access you grant

The key has account write capabilities. It is not a read-only reporting credential.

ToolsPurpose
get_dashboard, get_profileRead account summary, identity and stored settings
get_views, get_ordersRead recorded traffic and credited orders
get_payout_planRead balances, holds and payout readiness without requesting funds
get_media_kitRetrieve official kit information
update_profileChange supported profile fields
request_payoutCreate a request for the full available balance to the stored destination
delete_accountRequest supported account deletion; accounts with financial history require support

Tell the assistant which actions you authorize. Account and payout rules still apply through MCP. Device confirmation does not protect every account action, and connecting a client does not authorize a payout or deletion.

Reporting

Episode AFF 07 · Ask for a weekly report · 1:46 · KeepKey, step by step

Start with a request that states the period and limits:

Read my affiliate views, buy clicks and credited orders for the last seven days. State the exact dates and any result limits. Read my payout plan and distinguish pending from available commission. Do not request a payout or change my profile.

Compare the returned identity, dates and amounts with the same account in Reports. Ask the assistant to identify missing data rather than fill gaps with estimates.

Then ask it to retrieve the official media kit and draft one useful post answering an audience question. Keep the disclosed referral link in a follow-up reply and ask it to wait for review before publishing.

Replace, revoke or troubleshoot

  • No tools: confirm HTTP transport, endpoint and header, reconnect the client, then discover tools again.
  • Authentication fails: check whether the key was replaced or revoked. Do not paste the key into a support conversation or a screenshot.
  • Wrong account: stop and compare get_profile with the intended portal account before any write.
  • Lost key: the portal can show a newly issued key during that visit. Replace it when ready to update every client using the old key.
  • Disconnect: choose Revoke API key, remove the client configuration and verify a later account call fails. Revocation does not undo completed account actions.

If a key was exposed, revoke it promptly and reconnect with a new key. For any payout request, review the current amount and stored destination explicitly before instructing the assistant to submit it.

Last updated on