Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Governed MCP seller node: buyer agents discover inventory and register intents; no ad-server writes
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 7/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 7/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Gam Seller MCP Node。按照 https://mcp.popnx.com/i/juan-sibbo-gam-seller-mcp-node.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Node.js(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server Gam Seller MCP Node,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "gam-seller-node": { "command": "npx", "args": [ "-y", "gam-seller-mcp-node" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Gam Seller MCP Node 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"gam-seller-node": {
"command": "npx",
"args": [
"-y",
"gam-seller-mcp-node"
]
}
}
}用 Gam Seller MCP Node 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Gam Seller MCP Node,或回答中出现 Gam Seller MCP Node 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_CONFIG_DIR 保存 deployment.json/catalog.json/entitlements.json/pricing.json 的目录。省略此项则运行内置演示。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Gam Seller MCP Node
Gam Seller MCP Node 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Gam Seller MCP Node 的应用
B · 网店与支付 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server Gam Seller MCP Node,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user gam-seller-node -- npx -y gam-seller-mcp-node 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Gam Seller MCP Node 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user gam-seller-node -- npx -y gam-seller-mcp-node应能看到 Gam Seller MCP Node 在列表中并显示已连接
用 Gam Seller MCP Node 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Gam Seller MCP Node,或回答中出现 Gam Seller MCP Node 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_CONFIG_DIR 保存 deployment.json/catalog.json/entitlements.json/pricing.json 的目录。省略此项则运行内置演示。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server Gam Seller MCP Node,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "gam-seller-node": { "command": "npx", "args": [ "-y", "gam-seller-mcp-node" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Gam Seller MCP Node 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Gam Seller MCP Node 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Gam Seller MCP Node,或回答中出现 Gam Seller MCP Node 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_CONFIG_DIR 保存 deployment.json/catalog.json/entitlements.json/pricing.json 的目录。省略此项则运行内置演示。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Node.js(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server Gam Seller MCP Node,按顺序:1) 用 node -v 检查是否有 Node.js。没有的话,请让我从 https://nodejs.org/en/download 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "gam-seller-node": { "type": "stdio", "command": "npx", "args": [ "-y", "gam-seller-mcp-node" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 Gam Seller MCP Node 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
node -vMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: 打开官方下载页,选择 LTS 版本和点选式安装程序:Mac 用 .pkg · Windows 用 .msi。双击后一路下一步即可,不需要 curl 命令
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: node -v
安装一次,所有需要 Node.js 的工具都能用
用 Gam Seller MCP Node 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Gam Seller MCP Node,或回答中出现 Gam Seller MCP Node 的工具名称,就表示连接成功
上面的命令不填这些也能用。想调整时再按开发者的说明添加。
MCP_CONFIG_DIR 保存 deployment.json/catalog.json/entitlements.json/pricing.json 的目录。省略此项则运行内置演示。 说明为自动翻译,变量名保持原样;不确定时请查看原文。
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user gam-seller-node -- npx -y gam-seller-mcp-nodeClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"gam-seller-node": {
"command": "npx",
"args": [
"-y",
"gam-seller-mcp-node"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"gam-seller-node": {
"command": "npx",
"args": [
"-y",
"gam-seller-mcp-node"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"gam-seller-node": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gam-seller-mcp-node"
]
}
}
}MCP_CONFIG_DIR env说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 juan-sibbo 验证,该账户拥有此仓库
代码最后更新于2个月前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
OSV.dev 中没有 gam-seller-mcp-node@0.11.1 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月16日
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/juan-sibbo-gam-seller-mcp-node)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于2个月前,最新版本(0.11.1)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
Amazon Ads, Seller Central, Vendor Central and AMC data for AI agents. Read-only by default.
Search products, compare prices and discover deals across 6 European markets with your AI assistant.
| 本项 Gam Seller MCP Node | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Model Context Protocol server that exposes sell-side ad inventory to buyer-side AI agents: discovery, firm pricing, and a buyer-scoped soft commitment primitive. No writes to an ad server exist. Forecasts can come live from Google Ad Manager (opt-in, read-only ForecastService snapshot); the catalog is operator config, and without a GAM connection forecast data is synthetic.
Sell-side ad inventory (availability, pricing, product structure) lives inside ad servers that hold commercially sensitive and sometimes personal data. Giving an AI buyer agent direct API access to GAM or a similar system creates three risks:
| Risk | Without this project | With this project |
|---|---|---|
| Data over-exposure | Agent can read raw avails, deal IDs, exact floor prices | Only coarse buckets and pre-declared families |
| Accidental writes | Agent SDK can create orders, modify line items | No ad-server writes exist; the only write is a buyer's own soft commitment, which can never become a GAM order or an inventory hold |
| No accountability | API calls are logged but not auditable | Hash-chained audit ledger; every allow/deny recorded |
A buyer agent connects via MCP and gets five tools — three read-only, plus a buyer-scoped commitment primitive (create/revoke) that is the sole write surface:
Buyer agent
│ ├── well_known_capabilities ← Signed trust anchor. Check this first. │ Returns: RS256-signed capability document, node identity, privacy posture. │ ├── discover_products ← What can I buy here, and at what firm price? │ Returns: product families the buyer is entitled to see (e.g. "Pre-Roll Video"), │ each with its formats, channel and sites, and its firm list price │ when the publisher has configured them. │ Never returns: deal IDs, internal IDs, raw inventory, exact per-impression pricing. │ ├── get_forecast ← How available is this family next quarter? │ Returns: Low / Mid / High availability bucket. │ Never returns: exact impression counts, CPM curves, floor prices. │ ├── check_availability ← Can you deliver 2.8M impressions of this family in October? │ Returns: available / partial (up to ~2.7M, ~1.3M viewable) / unavailable, as of the │ last forecast — and, when it does not fit, where it would ("November: 3.1M"). │ Volumes come from the forecast rounded down to 2 significant figures │ (configurable by the publisher). │ Never returns: other buyers' bookings, floor prices, audience data. │ ├── create_intent ← Commit to a product at its current firm price (with TTL). │ Records a firm, time-boxed buying intent — rejected if the price is stale or │ mismatched. NOT a GAM order and NOT an inventory hold; it is the handoff artifact │ the classic sales rails pick up. Buyer-scoped: you can only ever commit as yourself. │ └── revoke_intent ← Withdraw one of your own active intents by id.
Every call flows through the same pipeline before any domain logic runs:
Buyer request
│ ▼ [SEC-GATE-3] Replay detection — deduplicate client_request_id │ ▼ [Auth] RS256 token validation → identity confirmed or AUTH_FAILED │ ▼ [Policy] Surface denylist → entitlement check → scope check (Default-Deny) │ ▼ [Rate limit] N=1 / T=30s per buyer_id │ ▼ [Domain] Catalog / ForecastEngine — synthetic, seeded or live GAM forecast snapshot │ ▼ [Disclosure] Response checked against the tool's strict schema — undeclared field → withheld │ ▼ [Audit] Append-only hash-chained ledger, buyer pseudonymized (HMAC) │ ▼ Response to buyer
Each request-path gate rejects on failure. One honest caveat to the diagram above:
MCP_REQUIRE_IDEMPOTENCY_KEY=0, which reopens that bypass.The rate-limit stage covers every authenticated tool — the read surfaces, create_intent, and revoke_intent — so no authenticated surface bypasses it.
A corrupted or tampered on-disk ledger is detected on startup and the node refuses to serve (fail-closed on load, plus a chain-integrity verify before the first request) rather than resetting to an empty chain.
create_intent runs the same gates and adds one more before it records anything: the buyer's price_ref must match the family's current firm price, or the request is rejected.
Run a full pilot in one command.
scripts/pilot.shbrings the node up on your config with
production guards on, mints a buyer token per entitled buyer, and prints how to drive a buyer
agent through the whole loop (discover → forecast → commit → revoke) — see
docs/PILOT-QUICKSTART.md. The reference buyer agent lives at
examples/buyer-client-ts/agent.ts; hosting behind TLS is a
filled-in-the-blanks recipe in
deploy/.
Add the server to your MCP client (Claude Desktop, Claude Code, Cursor, …):
{
"mcpServers": { "gam-seller": { "command": "npx", "args": ["-y", "gam-seller-mcp-node"] } } }
Or run it directly (stdio transport — the default for MCP clients):
npx -y gam-seller-mcp-node
Demo mode. With no config of your own, the node boots on a bundled
pilot-publisherexample (illustrative catalog, prices and forecasts) and says so
on stderr — it starts instead of failing, so you can try the tools immediately.
Because buyer surfaces always require a token (there is no anonymous path, even in
demo), the node prints a ready-to-use demo buyer token on startup: copy it and pass
it as the
tokenargument todiscover_products/get_forecastto see the example
families, prices and forecasts.
For a real deployment, point
MCP_CONFIG_DIRat a directory holding your own
deployment.json,catalog.json,entitlements.jsonandpricing.json:
`bash
MCP_CONFIG_DIR=/etc/gam-seller/config npx -y gam-seller-mcp-node
`
git clone https://github.com/juan-sibbo/gam-seller-mcp-node.git
cd gam-seller-mcp-node npm install npm run build npm run start:http # HTTP transport on 127.0.0.1:3900
Run the full buyer-agent walkthrough (scripted demo) — the five native tools driven over a real in-process MCP transport, ending in the governed refusals (fail-closed auth, Default-Deny, fail-closed pricing) and a verified audit chain:
npm run demo # or: npx tsx demo/run-demo.ts
docker compose up
The node starts on 127.0.0.1:3900. The well-known document is at /.well-known/seller-mcp-capabilities. Persistent volumes for keys and audit data are pre-configured in docker-compose.yml.
Four JSON files drive all publisher-specific behaviour — no code changes needed. Place them in config/ (from-source) or in the directory named by MCP_CONFIG_DIR (npx/containerised):
deployment.json # DSR contact, controller model, data retention window
catalog.json # product families + per-buyer access grants entitlements.json # which buyers are entitled to which MCP surfaces pricing.json # firm list prices per family (fail-closed on expiry) forecast.json # OPTIONAL — seed availability buckets from real numbers (still synthetic-labeled) gam.json # OPTIONAL — live GAM forecast (network, service-account key path, family → targeting)
Invalid config always fails closed: a malformed file stops the node rather than running with a silently different access policy. Absent config (no config/ and no MCP_CONFIG_DIR) drops to the bundled config/examples/pilot-publisher/ example — demo mode, announced on stderr — so the node is never a broken install, only ever a real deployment or a clearly-labelled demo.
Taking a pilot onto real inventory (short of a live GAM connection) is all configuration — see docs/PUBLISHER-DEPLOYMENT.md:
forecast.json (template: config/examples/pilot-publisher/forecast.sample.json). Buckets become realistic while every result stays synthetic: true — pre-loaded is not a live read, so no live-GAM claim is made.gam.json (template: config/examples/pilot-publisher/gam.sample.json) and a service account added to the GAM network with a read role that can run forecasts. The node asks ForecastService.getAvailabilityForecast for every configured family × period at boot and every 30 minutes, using prospective line items that are never saved — nothing in GAM is created, modified or reserved. Buyers are answered from that snapshot as Low/Mid/High buckets with synthetic: false; raw availability never leaves the node. Precedence: gam.json > forecast.json > synthetic.MCP_INTENT_HANDOFF=file (a local JSONL drop an operator forwarder tails). The handoff makes no outbound call — forwarding is the operator's process, and a URL value is refused. A handoff record is a notification, never a GAM order or inventory hold.MCP_REQUIRE_OPERATOR_CONFIG=1 (refuse to boot on demo config), MCP_ANCHOR_SINK=tsa (anchor the audit trail to a third party).Network egress — declared and bounded, not deny-all. Buyer request handling makes no outbound network calls. The live GAM forecast (gam.json) calls Google's OAuth token endpoint and the Ad Manager SOAP API for the configured network, at boot and on the 30-minute refresh cycle — never inside a buyer request, so buyers cannot generate load on the publisher's GAM. Optional audit anchoring can generate operator-configured egress outside the buyer request path (at boot and on the periodic anchor cycle): the TSA backend (MCP_ANCHOR_SINK=tsa) submits the ledger head hash to the configured RFC 3161 authority; the S3 backend (MCP_ANCHOR_SINK=s3) writes the anchor record to the configured Object Lock bucket; a custom sink module (MCP_ANCHOR_SINK= ) runs operator-supplied code. The default local anchor backend performs no external network call. Destinations come only from opera