The Cuelinks MCP server lets publishers and AI agents discover campaigns, convert any URL into a tracked link, and pull real-time earnings — right from Claude, Cursor, Windsurf, or any MCP-compatible client.
// Claude.ai → Settings → Integrations // → "Add custom connector" Server URL https://mcp.cuelinks.com Authentication Sign in with Cuelinks // or paste API key // Click Connect. 13 new tools appear — // convert_link, search_campaigns, // get_transactions, and 10 more — // with live access to 10,000+ campaigns. // Then ask Claude: // "search Amazon campaigns with good EPC"
Every snippet below is production-ready. Sign in with Cuelinks once for hosted clients, or pass your V3 API key for local ones — same auth, same tools.
Hosted clients like Claude.ai use the Sign in with Cuelinks flow — zero copy-paste. For local stdio clients, sign in at cuelinks.com → Settings → API Keys → Create V3 Key.
Non-technical? Use the Claude.ai tab — one URL, no terminal. Developers can also use the local npx wrapper for Claude Desktop, Cursor, or Windsurf.
Restart the client (or click Connect on Claude.ai). You should see cuelinks · connected with 13 tools registered. Ask your agent: "what can you do with cuelinks?"
Tools return JSON identical to the V3 API. Any agent workflow — research, authoring, reporting — can now reach live campaign data and produce tracked links.
Every tool maps 1:1 onto a Cuelinks V3 endpoint, so what works in your pipelines works in your agent — same schema, same rate limits, same auth. Discovery, linking, and reporting, all conversational.
Convert any product URL into a tracked clnk.in affiliate link with 5-dimensional sub-ID attribution.
Browse 10,000+ campaigns by category, country, access status, or free text. Sort by live EPC to find what's actually converting.
Query earnings, clicks, conversions, and sub-ID performance conversationally. Cursor-paginated so even months of data stream cleanly.
Everything else your agent needs to operate the Cuelinks surface end-to-end.
Convert many URLs in a single call, each with its own sub-ID set.
AI-powered: convert a URL and rewrite the surrounding title in one call.
Live coupons and deals across every campaign, filterable by category.
Performance, campaign, earnings, and unmonetized-traffic reports.
Invoices with tax breakdown plus the transactions linked to each.
Countries and categories for filter-building and discovery agents.
List, create, update, delete, and set-default for tracking channels.
Apply for private or restricted campaigns straight from chat.
File, update, or delete missing-transaction claims when sales drop.
Verify your API key and read back the publisher identity payload.
The MCP server is a thin, typed adapter over the Cuelinks V3 API. Your agent sees tools; the server handles auth, normalization, and rate limiting.
A user asks a natural-language question. Claude picks the right tool from the server's manifest — no custom orchestration needed.
cuelinks-mcp translates the tool call into a signed V3 request. Scoped keys, idempotent writes, low-latency JSON.
Results stream back in the native V3 schema. The agent reasons, writes copy, or plans the next tool call.
The server is transport-agnostic — stdio for local clients, Streamable HTTP for remote ones. If it speaks MCP, it speaks Cuelinks.
Add mcp.cuelinks.com as a connector and sign in with Cuelinks. Zero local install.
Drop the config into claude_desktop_config.json, restart, and call any tool from chat.
Run claude mcp add cuelinks. Every coding session can now pull live campaign data.
Ships in .cursor/mcp.json. Green-dot indicator shows all 13 Cuelinks tools are live.
Cascade picks up mcp_config.json. Use Cuelinks tools inside any agent workflow.
Use the mcp_servers field in the Messages API. Tools stream tool_use blocks inline.
Any MCP SDK (TypeScript, Python, Go, Ruby) can connect over stdio or HTTP. Standards-compliant, no lock-in.
sdkContinue, Cline, Zed, and any MCP-compatible tool Just Work. If it speaks the spec, it speaks to us.
communityMCP exposes the same scoped-key model as the V3 API. Issue a read-only key for browsing, a write key for monetization, rotate or revoke at any time.
Hosted clients (Claude.ai) use a one-click Sign in with Cuelinks flow that auto-fetches a session-scoped V3 key. Local stdio clients pass the key via CUELINKS_API_KEY env var; HTTP clients pass Authorization: Bearer.
Keys carry scopes. The MCP server honors them transparently — if your key can't write links, convert_link silently disappears from the tool list.
Three patterns we see weekly. Each is a single prompt away from being a real, tracked revenue stream.
Drop product mentions into your editor. Ask Claude to tag and convert them all at once — sub-IDs pre-filled for the issue.
Skip the dashboard. Let your agent rank campaigns by EPC across categories and countries before you invest a dev-hour.
No more SQL, no more pivot tables. Your finance team can query earnings, CR, and sub-ID performance with a sentence.
Your Cuelinks account already works. Paste the URL, sign in once, and your agent picks up 13 new tools with live access to every campaign on our rails.