linkpulse

Affiliate link & revenue intelligence for publishers — the first cross-network affiliate MCP server.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Revenue Summary: Total affiliate commissions for the current site over a window (default 30 days), with transaction count, average commission, and delta vs. the equivalent prior window. Data comes fro
  • Top Articles: Articles on the current site that generated the most commission over a window. URL grouping strips tracking parameters so the same article with different ?gclid= values is counted togeth
  • At Risk Articles: Articles that are earning affiliate commissions AND have broken affiliate links on the page — the revenue currently leaking each month. This is the cross-join between WeCanTrack reve

What data it sees

Do you need an account

No: the server works without sign-in

Affiliate link & revenue intelligence for publishers — the first cross-network affiliate MCP server.

Ask your AI agent what every article earns, which broken affiliate links cost the most money, and what to replace them with — across networks (Awin, Amazon, Daisycon, CJ and more, via the wecantrack integration).

Tools

  • revenue_summary — affiliate revenue totals + trend vs the prior window
  • top_articles — your highest-earning articles, ranked
  • at_risk_articles — revenue cross-joined with link health: where money is leaking
  • broken_links — full scanner state for your site
  • suggest_replacement — AI-picked working alternative for a dead affiliate URL

Setup

Get a license key at linkpulse.dev (free up to 500 links), then connect with the key as Authorization: Bearer or X-LinkPulse-License header. Works with WordPress sites (plugin), JavaScript snippet, or the direct API.

How to connect

How to connect linkpulse to Claude

The server address to paste into Claude settings:

https://linkpulse--joost-w2sc.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect linkpulse to ChatGPT

The server address to paste into ChatGPT settings:

https://linkpulse--joost-w2sc.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect linkpulse to Cursor

The server address to paste into Cursor settings:

https://linkpulse--joost-w2sc.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (5)

Raw names from tools/list. Only developers need these.

revenue_summaryTotal affiliate commissions for the current site over a window (default 30 days), with transaction count, average commission, and delta vs. the equivalent prior window. Data comes from WeCanTrack via the LinkPulse sync pipeline.
top_articlesArticles on the current site that generated the most commission over a window. URL grouping strips tracking parameters so the same article with different ?gclid= values is counted together. Use this to answer "which posts make money" and "where should I spend editorial time".
at_risk_articlesArticles that are earning affiliate commissions AND have broken affiliate links on the page — the revenue currently leaking each month. This is the cross-join between WeCanTrack revenue data and LinkPulse's local link scanner. Returns empty if the site has no broken links on earning articles. Use this to answer "where am I losing money" and prioritize fixes.
broken_linksAll broken affiliate links currently flagged by the LinkPulse scanner on this site. Status 4xx (dead) and 3xx (redirecting) are both included, grouped by post. Useful for audit-style questions and for piping into suggest_replacement.
suggest_replacementGiven a broken or dead affiliate URL plus the article it sits on, ask Claude (with web search) to find the closest-available alternative product on the same retailer or network. Returns a candidate URL, short reasoning, confidence, and a URL-reachability check. This is the "autonomous fix suggestion" that makes LinkPulse agent-native — the v1.1 apply_fix tool will consume this output directly.