rea
Reverse engineer anything with agents, from app behavior down to native binaries.
Webhook capture and replay, delivery pipes, and signed multi-agent rooms. No signup to start.
Skills that teach the AI this kind of work; they work alongside this one
Reverse engineer anything with agents, from app behavior down to native binaries.
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order
| 1. In Claude’s connector directory | No | |
|---|---|---|
| 2. Tried by our team | No | |
| 3. Works for Thai users | No | |
| 4. Usage without stars | 29/100 | Popularity 9 · Freshness 12 · Still answering 8 · Likes from users +0 |
| 5. Listed on | 2026-09-22 |
Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.
Quality: Passed 5/5 basic checks (shown, not used for ordering)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install FlurryPORT. Follow https://mcp.popnx.com/i/flurryport-webhooks-and-rooms.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 5/5 checks · What you ask goes through the maker’s server (mcp.flurryport.io) · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
FlurryPORThttps://mcp.flurryport.io/mcpClick Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add
+ConnectorsFlurryPORT
Use FlurryPORT and tell me what you can do for me, then show me one thing✓ If Claude says it is using FlurryPORT or shows a FlurryPORT tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
FlurryPORThttps://mcp.flurryport.io/mcpStart a new chat and pick FlurryPORT from your plugins before typing
Use FlurryPORT and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using FlurryPORT or shows a FlurryPORT tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --transport http --scope user webhooks-and-rooms https://mcp.flurryport.io/mcpYou should see FlurryPORT listed as connected
Use FlurryPORT and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using FlurryPORT or shows a FlurryPORT tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Use FlurryPORT and tell me what you can do for me, then show me one thing✓ If Cursor says it is using FlurryPORT or shows a FlurryPORT tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Use FlurryPORT and tell me what you can do for me, then show me one thing✓ If VS Code says it is using FlurryPORT or shows a FlurryPORT tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
https://mcp.flurryport.io/mcpJSON settings are under “For developers” below
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"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: flurryportBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026
The registry name was verified against the domain flurryport.io (the registry checks domain ownership)
Code last changed 6 days ago
Uses MIT
Responded in 953 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
No entries on OSV.dev for flurryport@0.6.12
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/flurryport-webhooks-and-rooms)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed 6 days ago, and the latest version (0.6.12) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP servers
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one FlurryPORT | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | MIT | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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.
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.
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
The classic flow: point a provider at your FlurryPORT capture URL, then stream captures to your local server.
npm install -g flurryport
flurryport login fp_your_token_here
flurryport target create
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
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
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.
| 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.
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.
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.
The privacy policy is at flurryport.io/privacy. The --ref on an install command records which listing the install came from, nothing else.
Node.js 22 or later is what the CLI is built and tested on.
MIT