Mcp Redtrack

io.github.pijuszPublished by GitHub account pijuszv0.1.4Updated Oct 24, 2026

MCP server for RedTrack affiliate tracking API

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query RedTrack affiliate tracking data such as campaigns, clicks, conversions, offers, and reports.

What you can do
This MCP server wraps the RedTrack affiliate tracking API and exposes 14 read-oriented tools. It can list and fetch campaigns (including a v2 endpoint), pull click and conversion logs with details like IP, country, device, payout, cost, revenue, and attribution, and return aggregated reports grouped by dimensions such as campaign, offer, country, date, or sub1-20. It also lists offers, traffic sources, affiliate networks, landing pages, and account settings.
When to use it
Use it when an assistant needs to inspect affiliate marketing performance in RedTrack, for example to review campaign status, dig into click or conversion logs, or summarize aggregated reports by dimension without leaving the chat client.
Requirements
Runs locally over stdio, typically via npx mcp-redtrack. Requires a RedTrack API key supplied as the REDTRACK_API_KEY environment variable; an optional REDTRACK_ENV_FILE variable points to a .env file. Network access to the RedTrack API is needed.
Before you install
The server needs a RedTrack API key (REDTRACK_API_KEY), which grants access to your affiliate tracking account data; store it in the client config or .env file rather than sharing it. Click and conversion logs include visitor-level details such as IP address and country, so querying them sends that data through the assistant. The listed tools appear to read data only, but confirm before relying on that.

Installation

In SourceWeft

  1. Open Mcp Redtrack in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[mcp-redtrack]

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

bash
npx mcp-redtrack setup YOUR_API_KEY

This prints the config snippet for your MCP client.

Claude Code

bash
claude mcp add redtrack -e REDTRACK_API_KEY=YOUR_API_KEY -- npx mcp-redtrack

Claude Desktop / Cursor

Add to your MCP settings JSON:

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

ToolDescription
get_campaignsList campaigns with filtering by title, status, source, tags, date range
get_campaignGet single campaign by ID with full config
get_campaigns_v2List campaigns via v2 endpoint

Logs

ToolDescription
get_clicksClick-level log with IP, country, device, campaign details (max 10k/page)
get_conversionsConversion log with payout, cost, revenue, attribution (max 10k/page)

Reports

ToolDescription
get_reportAggregated stats grouped by one or more dimensions (campaign, offer, country, date, sub1-20, etc.), with sorting

Entities

ToolDescription
get_offersList offers, filter by title, network, country, status, tags
get_offerSingle offer by ID
get_sourcesList traffic sources
get_sourceSingle source by ID
get_networksList affiliate networks
get_networkSingle affiliate network by ID
get_landingsList landing pages and prelandings
get_landingSingle landing by ID
get_streamsList streams
get_domainsList tracking domains
get_dictionaryReference lists: countries, currencies, timezones, browsers, OS, devices, ISPs, etc.
get_settingsAccount settings (timezone, currency, conversion types)

Environment variables

VariableRequiredDefaultDescription
REDTRACK_API_KEYYes—Your RedTrack API key
REDTRACK_ENV_FILENo.envPath to .env file

Development

bash
bun install          # install depsbun run dev          # run MCP serverbun test             # run testsbun run lint         # check formatting & lintbun run inspect      # open MCP inspectorbun run build        # compile standalone binarybun run build:npm    # bundle for Node.js / npm

License

MIT

Source: README.md at commit d23264a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts