World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Affiliate network reporting in your AI client. Bring your own keys. Most adapters experimental.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 11/100 | 热度 0 · 新鲜度 3 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-07-29 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/5 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Affiliate Networks MCP。按照 https://mcp.popnx.com/i/agenticaffiliate-affiliate-networks-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.agenticaffiliate.ai) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Affiliate Networks MCPhttps://mcp.agenticaffiliate.ai/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsAffiliate Networks MCP
用 Affiliate Networks MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Affiliate Networks MCP,或回答中出现 Affiliate Networks MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Affiliate Networks MCPhttps://mcp.agenticaffiliate.ai/mcp开启新聊天,输入前先从插件列表中选择 Affiliate Networks MCP
用 Affiliate Networks MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Affiliate Networks MCP,或回答中出现 Affiliate Networks MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user affiliate-networks https://mcp.agenticaffiliate.ai/mcp应能看到 Affiliate Networks MCP 在列表中并显示已连接
用 Affiliate Networks MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Affiliate Networks MCP,或回答中出现 Affiliate Networks MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Affiliate Networks MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Affiliate Networks MCP,或回答中出现 Affiliate Networks MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Affiliate Networks MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Affiliate Networks MCP,或回答中出现 Affiliate Networks MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.agenticaffiliate.ai/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user affiliate-networks https://mcp.agenticaffiliate.ai/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"affiliate-networks": {
"url": "https://mcp.agenticaffiliate.ai/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"affiliate-networks": {
"type": "http",
"url": "https://mcp.agenticaffiliate.ai/mcp"
}
}
}Claude Code
claude mcp add --scope user affiliate-networks -- npx -y affiliate-networks-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"affiliate-networks": {
"command": "npx",
"args": [
"-y",
"affiliate-networks-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"affiliate-networks": {
"command": "npx",
"args": [
"-y",
"affiliate-networks-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"affiliate-networks": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"affiliate-networks-mcp"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
发布者(agenticaffiliate.ai)不是仓库所有者(bobberrisford);可能是其他人代为上架的
代码最后更新于3个月前
使用 MIT
在 2227 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
OSV.dev 中没有 affiliate-networks-mcp@0.19.0 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/agenticaffiliate-affiliate-networks-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于3个月前,最新版本(0.19.0)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 Affiliate Networks MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/5 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Integrate your affiliate networks with Claude or Codex.
Network operators: most adapters are community-built and
experimental. Adoption gives your team ownership and a verification path; promotion topartialorproductionstill requires current evidence and maintainer review. Find your network's issue under theadopt-this-networklabel.
Affiliate networks have two sides — and neither has a first-class AI workspace integration.
Publishers earn commissions from the programmes they join. Brands (and the agencies who manage them) run those programmes and pay the commissions out. I wanted to chat to my own affiliate data in the AI workspace I already use; none of the networks had shipped an integration for either side, so I built a broad beta set that covers both publisher and advertiser-side work.
If you're a publisher, you can ask:
*"What did I earn across all networks last month?"*
*"Which programmes have transactions still pending after 90 days?"*
*"Compare my earnings month on month."*
If you're on the brand side — running a programme, or an agency managing several — you can ask:
*"How is Acme's programme doing this quarter?"*
*"Show me revenue across all my clients this week."*
*"Any anomalies in the affiliate data?"*
Your AI workspace figures out which networks to call, fetches the data live from their APIs, and gives you the answer. You can use Claude or Codex to turn it into a sheet, an artifact, an email to your boss, whatever you want.
Free and open source. MIT licensed. Bring your own keys. For the product philosophy, read the AI-native affiliate data manifesto.
This tool serves two audiences. Pick the one that fits — or both, if you wear both hats.
You're a publisher. You earn commissions from affiliate programmes, your dashboards can't keep up with how fast you can think, and you want one conversation that spans every network you're on.
You're on the brand side. You run an affiliate programme — or you're an agency managing several brands' programmes. You want one question that fans out across networks and brands, and surfaces what the dashboards bury: publishers trending down, reversal spikes, dead links, programmes drifting toward zero.
Either way, you do not need to know what an API is or write code. The non-technical Claude Desktop track needs:
The technical track uses a terminal, Node.js 20 or newer, and Claude Desktop, Claude Code, Codex, or another compatible local stdio MCP client; check the support states below before relying on an untested client journey.
And if you work for an affiliate network, this is also for you. The bundled adapters are placeholders until each network adopts its own. See CONTRIBUTING.md under "Adopting your network".
One question, every network and every brand. "Show me earnings by programme" hits your configured publisher networks in parallel. On the brand side, "show me revenue across all my clients this week" fans out across every brand and network pair you've registered.
Plain English, not filters. No more clicking through date pickers and saved views. "Last quarter, status pending, sorted by amount" is the whole prompt.
Your data, your machine, by default. It runs locally. Your keys live in ~/.affiliate-mcp/.env, locked to your user account. Optional anonymous usage telemetry is off by default and never contains affiliate data, credentials, prompts, arguments, results, or error text. The networks see the same API calls they'd see from their dashboard.
Catches what dashboards bury. Stale transactions, inactive programmes, dead deeplinks and week-on-week drops are surfaced by the packaged skills.
Optional local result cache. Persistent caching is off by default. Set AFFILIATE_MCP_CACHE=on in ~/.affiliate-mcp/.env to cache selected programme inventory and closed reporting windows locally with owner-only permissions. Open and current windows always go live. On a shared machine where you cannot rely on file permissions, leave caching off. Run affiliate-networks-mcp cache clear to remove cached results; see PRIVACY.md for the storage and retention contract.
Choose one of two primary tracks. Both run the same local MCP server and keep your credentials on your machine.
Use the host-native Claude Desktop .mcpb. No Terminal, Node.js, or manual configuration is required.
affiliate-networks-mcp- .mcpb from the latest GitHub release.The extension does not update itself: download the latest .mcpb and install it over the top; saved credentials are kept (full steps for every install path). The native extension currently offers secure setup fields for Awin, CJ, Impact, and Partnerize. It runs the complete server, so an existing ~/.affiliate-mcp/.env continues to enable every other adapter. A portable browser setup flow for the remaining networks is planned; until then, use the technical track below when adding them.
The standalone Electron/DMG setup app is a fixes-only compatibility fallback for existing macOS users. It is not a third primary onboarding track. See desktop/README.md for its remaining use case.
You'll need Node.js 20 or newer installed. If you don't have it, use the Node.js download page.
1. Run the setup wizard. Open Terminal (macOS) or PowerShell (Windows):
npx affiliate-networks-mcp setup
It walks you through one network at a time, asks which side you want, shows where to find each credential, then checks it against the live network.
For brand-side networks, the wizard asks which brands those credentials can reach, then lets you pick local nicknames. The mapping is saved to ~/.affiliate-mcp/brands.json, see Managing brands.
2. Check everything is wired up.
npx affiliate-networks-mcp test
You should see one line per network: ok for everything that's healthy, error — for anything that isn't.
3. Connect it to your local MCP client. Use a host-native package, the CLI installer, or local stdio configuration. The setup wizard offers the shipped CLI installer targets at the end automatically.
Claude Desktop (Mac/Windows app):
npx affiliate-networks-mcp install
Finds your Claude Desktop config, adds the affiliate entry alongside anything else you already have, takes a timestamped backup first. Restart Claude Desktop after it finishes. Flags: --desktop / --code / --codex to pick one, --all to include Codex and skip prompting, --dry-run to preview, --force-overwrite if your existing config is malformed JSON.
Claude Code (terminal):
claude plugin marketplace add bobberrisford/affiliatemcp
claude plugin install affiliate-networks-mcp@affiliatemcp
Registers the MCP server and bundled skills in one step. (Or use the install command above — it detects Claude Code too.) Already inside a Claude Code session? Just ask it to install the affiliate-mcp plugin and it runs these commands for you; no terminal juggling needed.
Codex (OpenAI, terminal or IDE extension):
npx affiliate-networks-mcp install --codex
This adds the local stdio MCP server to ~/.codex/config.toml; the same MCP config is used by the Codex CLI and Codex IDE extension. Manual setup:
codex mcp add affiliate -- npx -y affiliate-networks-mcp
Verify: open Codex, run /mcp, then ask "What affiliate networks do you have access to?" This is OpenAI/Codex support, not ChatGPT connector support. ChatGPT requires a reachable HTTPS MCP server and is scoped separately.
Claude Cowork desktop (org accounts):
Cowork syncs plugins from a GitHub repo, but blocks public repos from org marketplaces — so you need a private mirror first. The setup wizard offers this at the end, or run install and pick Cowork:
npx affiliate-networks-mcp install # detects your clients, offers Cowork
(Or go straight to it: npx affiliate-networks-mcp cowork-mirror.)
It creates /affiliatemcp-internal as a private repo and mirrors the upstream into it. If you have the GitHub CLI (gh) signed in, it's used automatically; otherwise it tells you exactly where to get a GitHub token and prompts you to paste it — the same "paste a credential" flow as setting up a network. Re-run with --sync to refresh against new releases.
Then, with org-admin access, in Cowork: Organization settings → Plugins → Add plugin → GitHub → enter /affiliatemcp-internal → install affiliate-networks-mcp from the synced marketplace.
Prefer to edit Claude Desktop config by hand?
Open the Claude Desktop config file at:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the affiliate entry inside mcpServers — keep any siblings:
{
"mcpServers": { "affiliate": { "command": "npx", "args": ["affiliate-networks-mcp"] } } }
Restart Claude Desktop after saving.
For another local stdio MCP client, configure the server command npx -y affiliate-networks-mcp. These clients are compatible in principle, not yet tested first-party journeys. Draft PR #49 is the existing VS Code/Copilot installer candidate.
These labels describe the onboarding journey, not whether every network adapter is live-verified. "Tested" means repository-owned automated validation, not live proof against every host version. See REPORT.md for maturity.
| Client or path | Support state | What that means |
|---|---|---|
Claude Desktop .mcpb | Shipped and release-tested | Primary non-technical path. CI builds and smoke-tests the bundle. Secure setup fields currently cover Awin, CJ, Impact, and Partnerize. |
| Claude Desktop CLI/manual config | Shipped and tested | Technical local stdio path. Installer/config behaviour has automated coverage. |
| Claude Code plugin and CLI registration | Shipped and tested | Technical path with packaged skills and local MCP registration. |
| Codex CLI and IDE extension | Shipped and tested | Technical path using the shared local Codex MCP configuration. This is not ChatGPT connector support. |
| Hosted connector (mcp.agenticaffiliate.ai) | Shipped and tested, paid | Remote MCP over OAuth, for people who cannot run the local server. Any client that can add a custom connector can use it, including Claude. Covers four networks (Awin, CJ, Impact, Rakuten), not every adapter. Read-only; credentials sit in an encrypted vault and browser-driven operations stay local-only. See PRIVACY.md an