- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 0.6.6
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
FlurryPORT MCP란?
FlurryPORT은(는) MCP server입니다. 웹훅을 캡처, 검사, 재생하고 서명된 멀티 에이전트 협업 룸을 관리합니다.
프로젝트 README에서 생성된 요약
FlurryPORT MCP server 정보
FlurryPORT는 네트워크 터널 없이 웹훅을 캡처, 검사 및 재생할 수 있는 특화된 환경을 제공합니다. Claude Code, Cursor 또는 VS Code와 같은 MCP 지원 에디터를 사용하는 개발자와 AI 에이전트를 위해 설계되었습니다. 이 MCP server를 통해 사용자는 Stripe, GitHub 또는 Shopify와 같은 외부 제공업체의 엔드포인트를 안정적인 캡처 URL로 지정하여 들어오는 이벤트를 모니터링할 수 있습니다. 사용자는 이러한 페이로드를 검사하고 JSONata를 사용하여 변환할 수 있으며, 원래의 서명을 유지한 채 로컬 애플리케이션으로 재생할 수 있습니다.
웹훅 관리 외에도 이 서버는 룸을 통해 서명된 멀티 에이전트 협업을 지원합니다. 룸은 여러 에이전트와 사람이 상호작용할 수 있는 공유되고 검증 가능한 기록을 제공합니다. 로컬 프로세스를 실행할 수 없는 호스팅 에이전트의 경우, seat server가 streamable HTTP 인터페이스를 제공합니다. 시스템은 계정이 필요하기 전까지 최대 250회의 캡처가 가능한 익명 세션을 지원합니다. 로컬 stdio 프로세스를 통해 작동하므로 로컬 명령을 실행할 수 있는 데스크톱 AI 클라이언트에 이상적입니다.
활용 사례
- 1웹훅 테스트 및 재생AI 에이전트가 제공업체 형식의 테스트 이벤트를 생성하고 이를 로컬 애플리케이션으로 재생하여 핸들러 로직을 검증할 수 있습니다.
- 2멀티 에이전트 협업개발자는 서명된 룸을 사용하여 여러 에이전트가 코드 리뷰나 작업 디스패치와 같은 작업에 참여할 수 있도록 할 수 있습니다.
- 3호스팅된 AI 모델 연결전용 seat server를 통해 ChatGPT 또는 Gemini와 같은 웹 기반 에이전트에 대한 액세스 권한을 부여할 수 있습니다.
- 4웹훅 루프 검증코드를 작성하기 전에 캡처 및 재생 루프가 제대로 작동하는지 확인하기 위해 로컬 에코 서버를 실행할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
FlurryPORT MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 FlurryPORT MCP 설치
$ claude mcp add cli -- npx -y flurryportCursor에 FlurryPORT MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"flurryport"
]
}
}
}VS Code에 FlurryPORT MCP 설치
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"flurryport"
]
}
}
}VS Code CLI에 FlurryPORT MCP 설치
$ code --add-mcp '{"name":"cli","type":"stdio","command":"npx","args":["-y","flurryport"]}'Claude Desktop에 FlurryPORT MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"flurryport"
]
}
}
}Codex에 FlurryPORT MCP 설치
$ codex mcp add cli -- npx -y flurryportCodex config.toml에 FlurryPORT MCP 설치
~/.codex/config.toml
[mcp_servers.cli] command = "npx" args = ["-y", "flurryport"]
Gemini CLI에 FlurryPORT MCP 설치
$ gemini mcp add -s user cli npx -- -y flurryportGemini settings.json에 FlurryPORT MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"command": "npx",
"args": [
"-y",
"flurryport"
]
}
}
}자동 검사
2026년 11월 15일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능flurryport/cli is public and reachablegithub.com/flurryport/cli ↗통과
- 패키지가 이 저장소를 소스로 명시flurryport names flurryport/cli as sourcenpmjs.com/package/flurryport ↗통과
- 빌드 출처(Sigstore 증명)No build attestation published for this release검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/flurryport/cli ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from flurryport통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음101 resolved dependencies checked; no critical advisoryosv.dev ↗통과
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기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 <invite> |
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 <name> and account remove <name>. |
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 <guest-name> |
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 <ref> 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
FlurryPORT MCP 질문
FlurryPORT MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add cli -- npx -y flurryport를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
FlurryPORT MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
FlurryPORT를 사용하려면 가입해야 하나요?
아니요, 계정 없이도 250회 캡처가 가능한 익명 세션으로 즉시 시작할 수 있습니다.
아직 실행 중인 백엔드가 없는데 웹훅을 어떻게 테스트할 수 있나요?
어시스턴트에게 에코 서버를 시작하도록 요청할 수 있습니다. 에코 서버는 핸들러 코드를 작성하기 전에 루프가 정상적으로 작동하는지 확인할 수 있는 로컬 수신기를 실행합니다.
FlurryPORT 룸이란 무엇인가요?
룸은 코드 리뷰나 디스패치와 같은 작업을 위해 여러 에이전트와 사람이 단일 서명된 기록을 공유하는 서명된 멀티 에이전트 협업 환경을 제공합니다.