About mcp-redtrack
mcp-redtrack is a read-only MCP server for querying RedTrack affiliate tracking data. It gives MCP-compatible clients tools for campaigns, activity logs, reports, and account entities.
Key features
- 01Read campaign lists and details
- 02Query click and conversion logs
- 03Group and sort performance reports
- 04Browse offers and tracking entities
- 05Inspect settings and reference data
Use cases
- 01Review campaign setup and status
- 02Analyze clicks and conversion attribution
- 03Compare performance across countries or dates
MCP support
Exposes 18 read-only tools to MCP clients for querying the RedTrack API; it does not modify the account.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
13Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| ids | string | No | |
| per | number | No | |
| page | number | No | |
| tags | string | No | |
| title | string | No | |
| status | string | No | |
| date_to | string | No | |
| sources | string | No | |
| timezone | string | No | |
| date_from | string | No | |
| total_stat | boolean | No |
Details
From the project README
mcp-redtrack
MCP server for the RedTrack affiliate tracking API. Query campaigns, clicks, conversions, and reports from any MCP-compatible client (Claude Code, Claude Desktop, Cursor, etc.).
Quick start
npx mcp-redtrack setup YOUR_API_KEY
This prints the config snippet for your MCP client.
Claude Code
claude mcp add redtrack -e REDTRACK_API_KEY=YOUR_API_KEY -- npx mcp-redtrack
Claude Desktop / Cursor
Add to your MCP settings JSON:
{
"mcpServers": {
"redtrack": {
"command": "npx",
"args": ["mcp-redtrack"],
"env": {
"REDTRACK_API_KEY": "YOUR_API_KEY"
}
}
}
}
Tools (18)
All tools are read-only (annotated with readOnlyHint); the server never modifies your RedTrack account.
Campaigns
| Tool | Description |
|---|---|
get_campaigns | List campaigns with filtering by title, status, source, tags, date range |
get_campaign | Get single campaign by ID with full config |
get_campaigns_v2 | List campaigns via v2 endpoint |
Logs
| Tool | Description |
|---|---|
get_clicks | Click-level log with IP, country, device, campaign details (max 10k/page) |
get_conversions | Conversion log with payout, cost, revenue, attribution (max 10k/page) |
Reports
| Tool | Description |
|---|---|
get_report | Aggregated stats grouped by one or more dimensions (campaign, offer, country, date, sub1-20, etc.), with sorting |
Entities
| Tool | Description |
|---|---|
get_offers | List offers, filter by title, network, country, status, tags |
get_offer | Single offer by ID |
get_sources | List traffic sources |
get_source | Single source by ID |
get_networks | List affiliate networks |
get_network | Single affiliate network by ID |
get_landings | List landing pages and prelandings |
get_landing | Single landing by ID |
get_streams | List streams |
get_domains | List tracking domains |
get_dictionary | Reference lists: countries, currencies, timezones, browsers, OS, devices, ISPs, etc. |
get_settings | Account settings (timezone, currency, conversion types) |
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
REDTRACK_API_KEY | Yes | — | Your RedTrack API key |
REDTRACK_ENV_FILE | No | .env | Path to .env file |
Development
bun install # install deps
bun run dev # run MCP server
bun test # run tests
bun run lint # check formatting & lint
bun run inspect # open MCP inspector
bun run build # compile standalone binary
bun run build:npm # bundle for Node.js / npm
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.