Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Auditable multi-agent topology generator from Drosophila MaleCNS connectome motifs.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://lm203688.github.io/flybrain-connectome/터미널에서 이 명령어를 실행하세요
claude mcp add --transport http flybrain-connectome https://lm203688.github.io/flybrain-connectome/프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"flybrain-connectome": {
"url": "https://lm203688.github.io/flybrain-connectome/"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"flybrain-connectome": {
"type": "http",
"url": "https://lm203688.github.io/flybrain-connectome/"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://lm203688.github.io/flybrain-connectome/메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
마지막으로 점검했을 때 서버가 응답하지 않아서 도구를 읽지 못했어요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 lm203688 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
점검할 때 6초 안에 응답하지 않았어요
점검할 때 6초 안에 응답하지 않았어요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 2개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(3.0.2)은 14일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, SwarmMemo
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
v3.01.3 · 2026-10-26 · 116 functional units · 270 module profiles · 64 gates · EPE 全栈 + AIBOM 供应链披露 + 收据完整性门禁 + Gate 60/61/62/63/64/65/66 + fail-loud 纪律 + 版本单一真源 + Xu 2026 树突计算前沿对照 + Xu 2026 双层认知计算参考实现(`tools/dendritic_rule_engine.py` + `examples/07_dendritic_rule_cache_demo.ipynb`)+ E4 区室边界 + S1 外部验证 + S2 lesion cascade + S3 统计强化 + 纪律有效性量化(catch-rate 100%,W1–W7 全部关闭)+ Gate 63 research_claims 顶层统计完整性 + 作者署名规范化(P-3 / P-4 → Li Xing + ORCID)+ bioRxiv 投稿准备包 + flybrain demo 一条命令 + 5 分钟上手 + flybrain audit CLI + JOSS 投稿包 + MCP 生态提交包 + 9 篇论文 DOI 补齐 + P1-3 HTTP/MCP 契约统一(Gate 66 · HTTP DISPATCH 从 12→47 全覆盖 MCP)+ P1-1 LangGraph runnable 后端(`--runnable` 生成含 MockLLM + MemorySaver checkpointing + OTel trace 的可执行 Python 脚本)
### The 89% problem
Deloitte's 2026 agent-pilot survey found **89% of enterprise agent pilots
never reach production**. Teradata: 78% have pilots, only 14% scaled. The
failure pattern repeats across industries in three words:
"跑不稳、管不住、查不清" — unstable, ungovernable, unauditable.
flybrain-connectomeaddresses the third word. Every agent edge in a
generated topology traces back to a real neuron or synapse class in the
*Drosophila* male brain connectome, serialized as W3C PROV-JSON — the
same format EU AI Act auditors expect. Your agent swarm isn't a black box;
it's a verifiable structure with biological provenance.
[5-minute quickstart](docs/QUICKSTART_5MIN.md) — from zero to an
interactive D3 topology graph in five minutes, no data download.
Auditable Agent Topology — 可审计的 Agent 拓扑生成与溯源, grounded in
the real *Drosophila* male-brain connectome (MaleCNS v1.0 — 166,700
neurons / 124,177,617 synapses, CC-BY).
flybrain-connectome turns a real, published brain wiring diagram into task-tailored multi-agent topologies you can instantiate as agent swarms — and it can prove, for every edge, *which real neuron / synapse class it came from*. The motif provenance is serialized as W3C PROV-JSON, the same standard EU AI Act auditors expect.
*5-module × 8-agent topology (predictive_coding_v2 blueprint) — the same graph you get from flybrain demo. Try it live →*
It is a developer toolkit and research artifact, not a trained model and not a simulation of a fly. Read the honest boundaries before you quote it.
Repo status: PUBLIC since 2026-10-18. History was audited and cleaned
before publicization (see CHANGELOG v1.3.0 for the original
Tier-2 IP leak and docs/D3_REPOSITORY_PUBLICITY_DECISION_2026-10-18.md
for the 16-step publicization runbook that was executed). The Tier-1 code is
MIT-licensed and reachable at https://github.com/lm203688/flybrain-connectome.
Tier-2 raw data (MaleCNS 5.63 GB, C. elegans Witvliet 2020, Drosophila larva
edges.csv, Petkova 2025 zebrafish) is fetched via the documented data pipeline
— see §"Requirements" and the S1 external-validation script.
| ✅ This project | ❌ Not this project |
|---|---|
| A connectome query service (47 tools over HTTP + MCP) | A spiking-neuron simulator |
| A motif-extraction pipeline (real fly → derived motif doc) | A repository of the raw 5.63 GB data |
| A synthetic topology generator (bio-motifs → agent graphs) | A trained / fine-tuned model with weights |
| W3C PROV provenance on every generated artifact | A claim that the "virtual organism" is alive |
The killer offline feature: `generate` needs no data — it composes topologies from a 7 KB derived motif snapshot. The connectome data is only needed if you want to *query* the real brain.
The 116 functional units are split cleanly by how their evidence comes together. This is the number to remember when reading any downstream claim:
| Bucket | Count | Meaning |
|---|---|---|
| Anchored to real *Drosophila* male-brain cells | 37 / 116 (31.9 %) | embodiment.real_cells_anchored > 0 — each edge traces to actual MaleCNS v1.0 neurons |
| Cross-species declarations, unanchored | 79 / 116 (68.1 %) | provenance.unanchored_reason = identity_not_in_drosophila or taxon_no_malecns_data — the circuit exists in the literature for another species, not in the MaleCNS connectome |
The 68.1 % bucket is not a defect and not a hidden error. It is a comparative-neuroscience scaffold: bird song, mammalian cortical layers, fish Mauthner, cephalopod vertical lobe, Aplysia and leech CPGs, insect mushroom-body — all are wired into the library with named references and can be composed like the anchored ones, but they are not measured in a real connectome the way the 37 anchored units are. Reading the library correctly means reading those two numbers together, not the 116 by itself.
Rather than a single "this is a X" pitch, the useful things this project does break down into three tiers. Which one you actually need depends on what you are building.
Tier 1 — usable today, offline, no data download. Neuron-circuit search across 3 species × 4 axes (system / function / species / provenance); compose a virtual-organism topology from any subset of units; run the four canonical DEMOs (mammal, insect, electrosensory, swim) end-to-end. This is the *developer tool* the project actually is. flybrain search, flybrain compose, flybrain generate cover it.
Tier 2 — for people designing AI-agent scaffolds. The composed topologies trace back to real circuitry via W3C PROV-JSON, which means a downstream agent framework (LangGraph / CrewAI / AutoGen / SwarmLabs) can pick up a starting topology and audit where each wiring decision came from. This is not a general agent infra — it is a biology-prior layer you plug into one.
Tier 3 — what this project explicitly does not do. It does not beat biology at anything (Phase 3 measured negative and is not claimed). It does not replace any EM reconstruction pipeline. It does not ship a trained model or a spiking simulator. If someone reads a v1.x changelog entry that promises any of those, the honest answer is "that was aspirational; the withdrawal is documented in docs/PROJECT_REALITY_ASSESSMENT.md".
We ran the experiments. Two of the "obvious" advantages turned out to be false under controlled testing, and we say so.
| # | Moat | Evidence | Status |
|---|---|---|---|
| 1 | Traceability — every generated edge traces to a real neuron/synapse class, serialized as W3C PROV-JSON | _verify.py 70/70; prov_json top-level field (schema v1.2.1) | ✅ real |
| 2 | Structural parsimony — genetic search finds far leaner graphs than the biological prior | GA converges to 9–11 edges vs 57 locked → −84% wire cost | ✅ real |
| 3 | Structural stability — module-level fault isolation | 25 / 27 sampled topologies show modular H1 isolation (92.6%); spectral radius ρ held at 0.00–0.30% | ✅ real |
| 4 | Local decision-making — modules read out their own answers | multi-readout experiment 5 / 28 H1 (17.9%), only on simple/delay≤2 tasks | ⚠️ partial |
| Dimension | Result | Why we dropped the claim |
|---|---|---|
| Raw compute advantage | 0 / 7 topologies beat random structure | Matched-control ESN calibration; motif advantage 0/7, differences within noise |
| Energy advantage | 0 / 24 runs beat random | SNN energy proxy; median ratio 1.006 (±5%), no systematic gain |
Honesty is a feature. The reproducible experiment scripts live in integrations/swarmlabs/diagnostics/ and the reports in the repo root (SNN_ENERGY_REPORT.md, MULTI_READOUT_REPORT.md, FAULT_ISOLATION_REPORT.md).
The toolkit needs one runtime dependency (numpy, because the connectome engine imports it at module level) plus optional extras for provenance and columnar IO. No other third-party code is required. Pick either setup:
Repo status: PUBLIC since 2026-10-18. No authentication required —
the clone commands below work directly. History was audited and cleaned
before publicization (see CHANGELOG v1.3.0 for the original
Tier-2 IP leak and docs/D3_REPOSITORY_PUBLICITY_DECISION_2026-10-18.md
for the 16-step publicization runbook).
git clone https://github.com/lm203688/flybrain-connectome.git
cd flybrain-connectome python flybrain_cli.py --help
flybrain on your PATH)git clone https://github.com/lm203688/flybrain-connectome.git
cd flybrain-connectome pip install -e . flybrain info
pip install -e . is *editable*: the flybrain entry point maps back to the checkout, which is precisely what lets it find the toolkit. A plain pip install . ships only the launcher, so point it at a checkout explicitly:
pip install .
export FLYBRAIN_HOME=/path/to/flybrain-connectome flybrain info
This path is verified in CI, not just documented. The
packagejob in
.github/workflows/ci.ymlrunspip install ".[prov]", invokes the console
script, resolves the toolkit via
FLYBRAIN_HOME, generates an organism, and
asserts the artifact's invariants — so the install instructions cannot
silently rot.
Structural provenance (motif_provenance, with the snapshot sha256) is always recorded. The *standardized* W3C PROV-JSON bundle (prov_json) is serialized by the optional dataprov package:
pip install dataprov # or: pip install "flybrain-connectome[prov]" (once on PyPI)
Without it the toolkit still runs: prov_json becomes null and get_provenance_bundle answers with prov_available: false plus the reason, rather than crashing. Both arms are asserted by scripts/check_degraded_mode.py — absent must degrade, present must actually produce the bundle.
flybrain info
reports the resolved toolkit root, the motif snapshot, the data dir, API-key status, and how many tools are exposed. Run it first whenever something looks wrong — it turns "ImportError" into a named, fixable problem.
MaleCNS v1.0 is CC-BY, ~5.63 GB, and deliberately not in this repo:
export FLYBRAIN_DATA_DIR=/path/to/your/male_cns
generate and the bundled motif snapshot need no data at all.
Every
flybrainbelow also works aspython flybrain_cli.py
(setup A), so you can try the project without installing anything.
###
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요