Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
Query web traffic and revenue attribution analytics with Google and Stripe integrations
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-09 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 RevScope。按照 https://mcp.popnx.com/i/revscope.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(api.revscope.co) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
RevScopehttps://api.revscope.co/v2/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsRevScope
用 RevScope 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 RevScope,或回答中出现 RevScope 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
RevScopehttps://api.revscope.co/v2/mcp开启新聊天,输入前先从插件列表中选择 RevScope
用 RevScope 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 RevScope,或回答中出现 RevScope 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user revscope https://api.revscope.co/v2/mcp应能看到 RevScope 在列表中并显示已连接
用 RevScope 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 RevScope,或回答中出现 RevScope 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 RevScope 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 RevScope,或回答中出现 RevScope 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 RevScope 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 RevScope,或回答中出现 RevScope 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://api.revscope.co/v2/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user revscope https://api.revscope.co/v2/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"revscope": {
"url": "https://api.revscope.co/v2/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"revscope": {
"type": "http",
"url": "https://api.revscope.co/v2/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 revscope.co 验证(注册中心会核实域名所有权)
代码最后更新于今天
不适用:由 revscope.co 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 241 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/revscope)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于今天,最新版本(0.1.0)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有: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.
| 本项 RevScope | Stripe MCP | flightclaw | Trade It | Marketplace Ad Pros: Amazon Ads & Seller Central | idealo MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 否 | 否 | 否 | 否 |
| 基础检查 | 4/4 | 4/4 | 4/4 | 5/5 | 4/4 | 4/4 |
| 许可证 | NOASSERTION | MIT | MIT | CC0-1.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
RevScope is revenue attribution analytics for websites. A small script on your pages records what visitors do (the pages they view, the searches and referrers that brought them, the events they trigger). RevScope then joins that activity to the payments they make in Stripe, Polar, Shopify, and other billing systems. The result shows which pages, channels, and campaigns actually bring in revenue, not just traffic.
There are two ways to use it:
Agents and scripts can set up the hosted service from the command line, with no browser: create an account, install the tracker, connect integrations, and query analytics. See cli/. MCP clients that only run local servers can reach the hosted MCP server through the Docker bridge in mcp-bridge/.
You need a machine with Docker and Compose v2. compose.yaml builds a single backend image that also serves the web app, and runs it next to Postgres.
cp docker.env.example .env
.env, fill in INTEGRATION_ENCRYPTION_KEY and POSTGRES_PASSWORD. The comments above each one show the command that generates it. docker compose up -d --build
The first build compiles the Rust backend and takes several minutes.
The backend listens only on 127.0.0.1:4320, so at first nothing outside the server can reach it. To put it on a public domain, choose one of these:
.env: COMPOSE_PROFILES=caddy
REVSCOPE_DOMAIN=analytics.example.com REVSCOPE_WEB_BASE_URL=https://analytics.example.com/ui
Run docker compose up -d again. Caddy gets a certificate from Let's Encrypt and serves HTTPS.
127.0.0.1:4320 and make sure the proxy sets the X-Forwarded-For header. The container reads the visitor's IP address from that header. This is safe only because nothing but this machine can reach port 4320, so don't publish the port more widely.REVSCOPE_WEB_BASE_URL matters in both cases, because it is the address used in emailed links such as invitations and password resets.
Copy the snippet from tracker/INSTALL.md into the of every page. The snippet sends data to the hosted service unless you give it your instance's URL, so add that URL as the third argument on its last line:
})(window, "examplecom", "https://analytics.example.com/");
examplecom stands for your project's name: the one you chose at signup, or for a project you add later, the name the dashboard shows.
Your data lives in two Docker volumes. revscope-data holds one SQLite file per project with the analytics events, and postgres-data holds logins, settings, and integrations. Back up both.
To upgrade, run git pull and then docker compose up -d --build. Database migrations run automatically on startup.
Every variable in .env is passed to the backend, so any option from revscope/.env.example works there too, such as email, AI chat, or error reporting. Run docker compose up -d after changing it.
Visitor locations (country and city) need MaxMind's free GeoLite2-City database, which can't be redistributed in this repository. Create a free MaxMind account and set MAXMIND_ACCOUNT_ID and MAXMIND_LICENSE_KEY in .env before building, and the build downloads the database and embeds it. If revscope/GeoLite2-City.mmdb already exists in the checkout, the build uses that file instead. Without either, geolocation is turned off.
A self-hosted instance has one account, and every user sees all of its projects. Signup creates the first project, named as you choose, and you can add more from the dashboard. After the first person signs up, they invite others from Settings. An invitation link lets the invited person choose a password and expires after 7 days, and someone who hasn't accepted 30 days after their latest invitation is removed, so they stop reserving their email address. RevScope emails the link if email is configured (MAILCHANNELS_API_KEY and MAILCHANNELS_FROM_EMAIL), and Settings always shows it so you can send it yourself.
The hosted service's plan limits don't apply. There is no cap on events and no monthly budget for AI chat. Links to documentation point at revscope.co.
The self-hosted build is a single binary. It contains the backend, the web app, the tracker script, the database migrations, and optionally the GeoLite2 database. You need the prerequisites installed. Build it like this:
(cd web && pnpm install && pnpm build:bundle)
cd revscope && cargo build --release --bin revscope --features self-hosted
The binary is revscope/target/release/revscope. Build it on a machine with the same OS and CPU architecture as your server, or cross-compile.
To run it:
createdb revscope).revscope/.env.example to .env in the directory you will run the binary from, and fill it in. Only DATABASE_URL and INTEGRATION_ENCRYPTION_KEY are required. Set REVSCOPE_WEB_BASE_URL to your public URL followed by /ui, for example https://analytics.example.com/ui.REVSCOPE_TRUST_X_FORWARDED_FOR=true so visitor IPs come from the proxy's X-Forwarded-For header. Make sure the backend's port can be reached only through the proxy, because otherwise anyone could forge that header.The web app is served under /ui, and / redirects to /ui/dashboard. It calls the API on the same origin, so no cross-origin (CORS) setup is needed. Project databases are stored in data/ inside the working directory, so back up that directory along with Postgres.
Instead of a reverse proxy, the backend can serve HTTPS itself with certificates from Let's Encrypt. Set REVSCOPE_LISTEN_TLS=0.0.0.0:443, REVSCOPE_LISTEN=0.0.0.0:80 (Let's Encrypt validates the domain over port 80), and REVSCOPE_TLS_DOMAINS to your hostname, for example analytics.example.com. Binding ports below 1024 as an unprivileged user needs the CAP_NET_BIND_SERVICE capability.
The backend sends Strict-Transport-Security for the hostnames in REVSCOPE_WEB_BASE_URL (or the older APP_BASE_URL) and REVSCOPE_API_BASE_URL when they start with https://, and for REVSCOPE_TLS_DOMAINS when it serves HTTPS itself. For a year after a visit, browsers then refuse plain HTTP to that hostname on every port, so don't serve anything else over plain HTTP on it.
The backend reads its settings from environment variables, and also from a .env file in its working directory. Real environment variables take precedence. revscope/.env.example lists every option with a comment explaining it. The main groups are:
| Variables | Purpose |
|---|---|
DATABASE_URL, INTEGRATION_ENCRYPTION_KEY | Required: the Postgres URL and the credential key |
REVSCOPE_LISTEN | Address for plain HTTP (default 127.0.0.1:4320) |
REVSCOPE_WEB_BASE_URL, REVSCOPE_API_BASE_URL | Public URLs used in emailed links and MCP metadata |
REVSCOPE_TRUST_X_FORWARDED_FOR | Read visitor IPs from a reverse proxy's header |
REVSCOPE_MAX_CONNECTIONS | Connection cap (100,000, or less if ulimit -n is low) |
MAILCHANNELS_API_KEY, MAILCHANNELS_FROM_EMAIL | Sending email (invitations, password resets) |
REVSCOPE_GOOGLE_CLIENT_ID, REVSCOPE_APPLE_CLIENT_ID | Sign in with Google and Apple, hidden unless configured |
REVSCOPE_GOOGLE_CLIENT_ID, REVSCOPE_GOOGLE_CLIENT_SECRET | "Connect with Google" for Google Analytics imports |
REVSCOPE_CHAT_URL, REVSCOPE_CHAT_API_KEY, REVSCOPE_CHAT_* | The AI chat tab, which is hidden unless configured |
SENTRY_DSN | Error reporting to Sentry |
REVSCOPE_CORS_ORIGINS | Hosts of a web app deployed separately from the backend |
REVSCOPE_LISTEN_TLS, REVSCOPE_TLS_DOMAINS, REVSCOPE_ACME_* | Built-in HTTPS with Let's Encrypt certificates |
REVSCOPE_REQUIRE_CLOUDFLARE | Settings for the hosted service's servers |
REVSCOPE_MCP_DEMO_TOKEN | An rsm_ MCP token that reads only the public demo |
INTEGRATION_ENCRYPTION_KEY encrypts the API keys you enter for integrations such as Stripe before they are stored. If you lose it, those keys can't be decrypted and have to be entered again.
The AI chat tab sends requests to an OpenAI-compatible chat completions endpoint. It was built for Cloudflare AI Gateway forwarding to xAI, so REVSCOPE_CHAT_GATEWAY_TOKEN is sent as Cloudflare's cf-aig-authorization header and the default model is grok/grok-4.7.
The repository has these parts:
| Directory | What it is |
|---|---|
tracker/ | tracker.js, the single-file ES5 script that site owners embed on their pages. |
revscope/ | The Rust backend: event ingest, the query API, accounts, and integrations. SQLite per project, Postgres for accounts. |
web/ | A pnpm workspace with the web app (web/app, Astro and Solid) and its auth client (web/shared). |
cli/ | The revscope command line tool, which calls only the HTTP API. |
mcp-bridge/ | A Docker bridge to the hosted MCP server, for MCP clients that only run local servers. |
crates/revscope-api/ | The HTTP contract the backend and the CLI share: request and response types, route paths, and limits. |
e2e/ | Playwright tests that drive the public demo dashboard. They only read. |
See CONTRIBUTING.md for code conventions, the checks to run, and how to send a pull request.