Home/Docs/MCP server (for Claude, ChatGPT, Cursor)
Docs

MCP server (for Claude, ChatGPT, Cursor)

Connect Claude Desktop, ChatGPT, Cursor, or any MCP-compatible agent directly to your Trcker brand. Ask questions and run operations in natural language.

What it is

Trcker ships a remote Model Context Protocol server at https://trcker.io/api/mcp. Any MCP-compatible AI client can connect to it, scope itself to your brand via an API key, and read your affiliate performance data or run operational tasks (create offers, pause partners, adjust payouts, approve conversions, set caps) — all in natural language.

No SDK. No separate login. Just paste a config snippet and go.

What agents can do

Read (5 tools): - get_partner_stats — performance by partner - get_offer_stats — performance by offer with pending/approved/paid breakdowns - get_conversions — recent conversions, filter by status - get_fraud_summary — scored/flagged counts + top-risk partners - get_top_publishers — rank partners by revenue, conversions, EPC, CVR, or profit

Write (5 tools, audit-logged): - create_offer — spin up a new offer with payout rules - pause_partner — pause a partner brand-wide - adjust_payout — set per-partner payout overrides on an offer - approve_conversion — manually approve a conversion (also clears its fraud signal) - set_cap — adjust daily/weekly/monthly caps on an offer

Every write emits a WorkOS audit event tagged to a synthetic mcp: actor so your audit log cleanly separates agent-driven writes from dashboard writes. Your IP and user-agent are forwarded into the audit context.

Setup — Claude Desktop

  1. Generate a brand API key at Settings > API Keys.
  2. Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
  3. Add:

`json { "mcpServers": { "trcker": { "transport": { "type": "streamable-http", "url": "https://trcker.io/api/mcp", "headers": { "Authorization": "Bearer trk_..." } } } } } `

  1. Restart Claude Desktop. The Trcker tools appear in the tool picker automatically.

Example prompts

` Which partners have the highest fraud scores this month? `

` Show me top 5 publishers by revenue in the last 14 days. `

` Pause partner abc-123 and lower their payout on offer xyz to 15%. `

` Approve conversion conv_9f2a if its fraud score is under 20. `

Claude will call the right tool, pass the right arguments, and summarize the result in context.

Safety

  • Every write tool is scoped to your brand — a key for Brand A can't touch Brand B.
  • Caps are soft by defaultpause_partner doesn't cancel pending conversions, it just stops new click-throughs.
  • Rate-limited — 120 requests per minute per API key. Agents that spam get 429'd, not data-exfiltrated.
  • Confirmation hints — write tools carry destructiveHint / idempotentHint annotations so MCP clients can surface a harder confirm dialog before invoking.

Protocol details

  • Streamable HTTP transport (no SSE, stateless).
  • Protocol versions: 2025-06-18, 2025-03-26, 2024-11-05.
  • JSON-RPC 2.0 at the wire — single or batched.
  • Manifest available at GET /.well-known/mcp-manifest for auto-discovery.

Full protocol + tool reference: docs/mcp.md on GitHub.

Example — raw JSON-RPC

`bash curl -s https://trcker.io/api/mcp \ -H "Authorization: Bearer $TRCKER_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_top_publishers","arguments":{"metric":"revenue","limit":5}}}' `

Related

  • API — REST interface for integrations that don't speak MCP
  • Fraud detection — what get_fraud_summary actually surfaces
  • Integrations — connect to ad platforms + CRMs alongside MCP