Tracking Integration Agent Hackathon project

PI Live BuildLab

Your affiliate tracking integration copilot.

A free MCP server that brings affiliate tracking expertise into the AI tools your team already works in. No waiting on specialist resources, no long implementation cycle — just structured guidance for Awin, impact.com and Tradedoubler, tailored to your stack. Built as an open solution for the entire affiliate industry. More networks can be added.

Early pilot, built in one day — always check the official documentation.

MCP endpoint https://integration-mcp.awin.com/mcp

Why it exists

Affiliate tracking integrations are slow, fiddly and easy to get subtly wrong. This turns that scattered knowledge into a decision layer your assistant can actually follow.

Expertise where you already work

Guidance arrives inside your IDE or chat window instead of a support ticket, so nobody waits on a specialist to unblock the build.

It reads your environment first

Shopify, WooCommerce, GTM or a custom build — it asks the intake questions that change the answer, then recommends the method that fits your access.

A plan, not a pile of docs

You get ordered installation steps and ready-to-use tracking snippets, linked back to the network's official documentation.

Proof it actually works

Built-in verification checks confirm tracking quality after deployment, cutting the revenue leakage and debugging time that follow a silent misconfiguration.

Set it up

Takes about a minute. No account, no API key, nothing to install.

Project: .cursor/mcp.json · Global: ~/.cursor/mcp.json 

{
  "mcpServers": {
    "tracking-integration": {
      "url": "https://integration-mcp.awin.com/mcp"
    }
  }
}

Reload Cursor, then confirm it under Settings → Tools & MCP.

One command in your terminal

claude mcp add --transport http \
  tracking-integration \
  https://integration-mcp.awin.com/mcp

Add --scope user to enable it in every project. Verify with claude mcp list.

Settings → Connectors → Add custom connector

https://integration-mcp.awin.com/mcp

Paste the URL as a custom connector. claude_desktop_config.json only speaks stdio, so use the connector rather than the config file.

Workspace: .vscode/mcp.json

{
  "servers": {
    "tracking-integration": {
      "type": "http",
      "url": "https://integration-mcp.awin.com/mcp"
    }
  }
}

VS Code uses servers, not mcpServers.

Once connected, just describe your situation in plain language — "help me set up Awin tracking on my Shopify store". You never need to name a tool yourself.

What a session looks like

The planner asks before it assumes, and never invents steps for a network it does not cover.

Help me set up Awin tracking for my Shopify store.
Do you have Shopify admin access, and are you allowed to install a third-party app?
Admin yes, but I can't install apps. We do have GTM.
What is your advertiser ID in Awin?

Coverage and boundaries

Three networks today, on an open registry format so more can be added as data, not code.

Networks

Awin, impact.com and Tradedoubler — each with its own intake questions, methods and verification checks.

Platforms

Shopify, WooCommerce and custom sites, covering app and plugin installs, Google Tag Manager, theme code and server-to-server.

Plans and verifies only

The server never executes anything. It holds no credentials and never sees your code. Your own tools do the work.

Says so when it doesn't know

Outside its registry it tells you plainly rather than improvising steps, because guessed tracking breaks attribution silently.

Bring your network

Open to every affiliate network — adding one is a data exercise, not an engineering project.

Send us your integration guides

If you run or work with a network that isn't covered yet, share your official integration documentation and we'll add it to the registry so the whole industry can use it.

global-producttracking@awin.com