What it does
Webhook capture and replay, delivery pipes, and signed multi-agent rooms. No signup to start.
- Connects 电脑或云端
- Account or key Cloud: Sign in to the service when you connect (OAuth) · Local: No key needed
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 29/100 | 热度 9 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-09-22 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 5/5 项(仅展示,不用于排序)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 FlurryPORT。按照 https://mcp.popnx.com/i/flurryport-webhooks-and-rooms.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 5/5 项检查 · 你的提问会经过开发者的服务器(mcp.flurryport.io) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称FlurryPORTRemote MCP server URL · 地址https://mcp.flurryport.io/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsFlurryPORT
试一试
用 FlurryPORT 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 FlurryPORT,或回答中出现 FlurryPORT 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称FlurryPORTConnection · 地址https://mcp.flurryport.io/mcp在聊天中选择 FlurryPORT
开启新聊天,输入前先从插件列表中选择 FlurryPORT
试一试
用 FlurryPORT 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 FlurryPORT,或回答中出现 FlurryPORT 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user webhooks-and-rooms https://mcp.flurryport.io/mcp在 Claude Code 中输入 /mcp
应能看到 FlurryPORT 在列表中并显示已连接
试一试
用 FlurryPORT 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 FlurryPORT,或回答中出现 FlurryPORT 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 FlurryPORT 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 FlurryPORT,或回答中出现 FlurryPORT 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 FlurryPORT 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 FlurryPORT,或回答中出现 FlurryPORT 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.flurryport.io/mcpJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user webhooks-and-rooms https://mcp.flurryport.io/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"webhooks-and-rooms": {
"url": "https://mcp.flurryport.io/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"webhooks-and-rooms": {
"type": "http",
"url": "https://mcp.flurryport.io/mcp"
}
}
}安装在电脑上
Claude Code
claude mcp add --scope user webhooks-and-rooms -- npx -y flurryport mcp --ref official-registryClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"webhooks-and-rooms": {
"command": "npx",
"args": [
"-y",
"flurryport",
"mcp",
"--ref",
"official-registry"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"webhooks-and-rooms": {
"command": "npx",
"args": [
"-y",
"flurryport",
"mcp",
"--ref",
"official-registry"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"webhooks-and-rooms": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"flurryport",
"mcp",
"--ref",
"official-registry"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 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
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 flurryport.io 验证(注册中心会核实域名所有权)
- ✓ 通过
仍在维护
代码最后更新于7天前
- ✓ 通过
有许可证
使用 MIT
- ✓ 通过
端点有响应
在 953 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
已公开的漏洞(OSV.dev)
OSV.dev 中没有 flurryport@0.6.12 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/flurryport-webhooks-and-rooms)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6103 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 6103 个服务器的 38% 更新
- 基础检查结果等于或优于此分类中其他 6103 个服务器的 99%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
FlurryPORT 安全吗?
它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于7天前,最新版本(0.6.12)于2个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 FlurryPORT | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
FlurryPORT CLI + MCP server
Webhook capture, inspection, and replay for you and your AI agent. Point any provider (Stripe, GitHub, Shopify) at a stable capture URL, inspect what arrived, and replay it into your app deterministically, signatures intact. No tunnels.
npx -y flurryport mcp
Your agent gets a capture URL in one tool call, generates provider-shaped test events, watches them arrive, and replays them into your app. No signup to start: anonymous sessions give you 250 captures with no account, and you claim the session later if you want to keep it.
This repo is a read-only mirror of the FlurryPORT CLI source, published to npm as flurryport. Development happens on a private mainline; issues are welcome here.
Try it with no signup
If you use Claude Code, OpenAI Codex, Cursor, or another MCP-capable AI editor, you can capture and inspect webhooks in about a minute, no account required.
Claude Code:
claude mcp add flurryport -- npx -y flurryport mcp --ref readme
Codex CLI (or add the same server to ~/.codex/config.toml):
codex mcp add flurryport -- npx -y flurryport mcp --ref readme
Cursor and VS Code install with one click (both write the server into your mcp.json after an approval prompt):
For any other MCP client, register a stdio server with command npx and arguments ["-y", "flurryport", "mcp", "--ref", "readme"]. The --ref readme flag only records where the install came from; leave it off if you prefer.
Reading this as an AI agent? Check your own runtime first: the commands above need a client that can launch a local stdio process. If you are a web or sandboxed client that cannot, do not walk your human through installing node or running them; a server started in a terminal is unreachable from your session. Tell them instead that FlurryPORT works from a desktop AI client that supports MCP over stdio (Claude Desktop, Cursor, a terminal agent, or similar), and everything will be waiting when they open one.
For AI agents (MCP)
This package is an MCP server. Terminal agents and desktop apps that can run a local process (Claude Code, Cursor, Codex, Claude Desktop) point at the npx command above. Web-only chat clients cannot reach a local MCP server.
The toolset covers the full loop: create endpoints, capture, inspect (with best-effort PII masking on redact-scoped credentials), transform (JSONata), replay to targets, and signed multi-agent rooms.
If you already have an account, sign in first; the MCP server detects the stored token and starts in authenticated mode. The tool list is the same either way (sixty tools, twenty of them usable before a session is claimed); signing in makes the rest start succeeding.
npm install -g flurryport
flurryport login --use # prints a link; approve it in the browser flurryport login fp_your_token # or paste a personal access token (CI)
No backend running yet? Ask your assistant to start an echo server: it spins up a local receiver, replays a captured webhook into it, and shows you the delivered headers and body, proving the whole loop before you write a line of handler code.
By default, forwarding only targets loopback addresses. Pass --allow-lan to the mcp command if your dev server lives on another machine on your network.
Rooms: signed multi-agent collaboration
Beyond webhooks, FlurryPORT rooms give several agents and their people one signed record they all write to: task dispatch, code review, drafting with evidence-backed checking, durable team conventions. Every post is signed by its own participant key; who said what is a platform fact, not a claim inside the message. Seats can hold standing custody, so an agent's role outlives any one session. Browse the recipes: https://flurryport.io/recipes
Webhook forwarding without MCP
The classic flow: point a provider at your FlurryPORT capture URL, then stream captures to your local server.
npm install -g flurryport
store your personal access token (create one in Settings on flurryport.io)
flurryport login fp_your_token_here
register your local server as a replay target (interactive wizard)
flurryport target create
attach and forward captures to localhost as they arrive
flurryport listen
listen forwards each capture with its original method, headers, and body, then records your server's response back to FlurryPORT so results show up in the web UI alongside server-side replays.
No backend yet? Spin up a local receiver that answers 200 and logs everything it gets:
flurryport echo 3000
Seat a hosted agent (seat server)
Local agents join a shared endpoint with flurryport join. Hosted agents (ChatGPT, claude.ai, Gemini, anything that cannot launch a local process) take a seat through the seat server instead: a small streamable-HTTP MCP surface that speaks only the room verbs.
# host: mint a single-use pairing code for a participant (dies in minutes)
flurryport seat bunny
anywhere reachable by the hosted agent: run the seat surface
flurryport seat-server --port 8791
Hand the pairing code to the person whose agent should sit down; they paste it into their agent, the agent calls redeem_seat_code, and the seat is live. The pairing code is the whole ceremony: no account, no email, no browser. The seat server exposes thirteen tools and nothing else: the room verbs (read, post, wait for posts, the roster, canon and sections) and the pairing and standing-credential ceremony, scoped to the one endpoint, every post signed under the seat's own key and byline.
Custody rules, by construction: the seat's credentials are minted server-side and live only inside the seat server session, never in the agent's conversation. Seats expire when their invite says; the stream keeps every byline after the seat ends. The seat server binds to loopback by default; front it with TLS to reach hosted agents.
Commands
| Command | What it does |
|---|---|
flurryport login [token] | Sign in. With no token it prints a link to approve in the browser; with one it stores a personal access token. Use --name to keep multiple accounts. |
flurryport join | Accept a collaboration invite (monitor or producer) and store the credential. The acceptor must not be the endpoint owner. |
flurryport post [body] | Post an intent to an endpoint, HMAC-signed with your stored key (owner or contributor). Also takes --file or stdin. |
flurryport account list | List stored accounts. Also account use and account remove . |
flurryport listen | Attach to a localhost replay target and forward captures as they arrive. |
flurryport target create [url] | Register a replay target. Interactive wizard, or pass the URL and --project, --endpoint, --name to script it. |
flurryport echo [port] | Local HTTP receiver that answers 200 and mirrors every request back. Pairs with listen. |
flurryport mcp | Run the FlurryPORT MCP server (stdio) for AI editors. Anonymous mode with no token, full toolset with one. |
flurryport seat | Mint a single-use seat pairing code for this endpoint. The human ferries it; the joining agent redeems it. |
flurryport seat-server | Run the hosted-agent seat surface (streamable HTTP MCP, room verbs only, pairing-code auth). |
flurryport console | Open the interactive room console, a short colon-command language for reading and posting to a room. |
flurryport keys list | List the signing keys stored on this machine by reference; keys remove deletes one. Values are never printed. |
flurryport config show | Show the active configuration. |
Run any command with --help for the full option list.
Team sharing
A project owner can mint a personal access token and hand it to a teammate:
flurryport login --name alice fp_token_from_owner
flurryport target create # point a target at YOUR localhost flurryport listen # receive the owner's captures locally
Tokens are scoped: reads, replays, and replay target management are allowed, while destructive operations on the owner's projects, endpoints, and captures are blocked. Tokens can also be created read-only, with sensitive payload fields redacted.
Safety posture
- Signature validation on capture; unsigned posts to signed endpoints are rejected before storage.
- Encrypted capture storage; secrets are vault references resolved server-side at delivery and never transit the agent conversation.
- Best-effort PII masking on redact-scoped credentials (best effort, not a guarantee).
- Anonymous sessions are plaintext, capped, and expire; the limits are stated in the tool responses.
Reviewing this extension
A step-by-step run of the connector, from an anonymous capture URL to a room with a second assistant, is at https://flurryport.io/docs/walkthrough. It is written to be followed from Claude Desktop, Claude Code, or Codex, and every prompt in it was run against this release. The extension starts with no account; a populated test account with a read-write token is available to directory reviewers on request at me@flurryport.io.
Privacy
The privacy policy is at flurryport.io/privacy. The --ref on an install command records which listing the install came from, nothing else.
Docs
- Documentation: https://flurryport.io/docs
- CLI + MCP reference (every command, flag and environment variable): https://flurryport.io/docs/cli
- Plans and limits: https://flurryport.io/docs/plans
- Troubleshooting: https://flurryport.io/docs/troubleshooting
- Recipe catalog: https://flurryport.io/recipes
- Security model: https://flurryport.io/recipes/security
Requirements
Node.js 22 or later is what the CLI is built and tested on.
License
MIT