Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
SYNAPSE CHANNEL
Overview
Description from the maker (original English)
Local-first multi-agent coordination for messages, leases, shared plans, status, and resources.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"synapse-channel": {
"command": "uvx",
"args": [
"synapse-channel"
]
}
}
}Run this in your terminal
claude mcp add synapse-channel -- uvx synapse-channelOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"synapse-channel": {
"command": "uvx",
"args": [
"synapse-channel"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"synapse-channel": {
"type": "stdio",
"command": "uvx",
"args": [
"synapse-channel"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account anulum, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32680 servers in this category
- Published to the registry more recently than 92% of the other 32680 servers in this category
- Basic checks equal to or better than 100% of the other 32680 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is SYNAPSE CHANNEL safe?
It passed 1 of 1 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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.99.45) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
EmbeddedCI BenchPod
by embeddedci-com
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Runs on your computerUpdated today
Install
README from the maker
Open the README
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.
The local-first coordination bus for fleets of AI agents.
One WebSocket hub is the shared source of truth for presence, file-scope claims, a shared plan, task status, and capabilities — for agents working in one repository or across a whole ecosystem of them.
Flagship example: coordinate parallel AI coding agents through declared file scopes — the hub refuses a second overlapping live claim, while covered provider hooks and the staged Git gate enforce only their documented mutation boundaries.
English · 简体中文 · Español · Português (Brasil) · 日本語 · 한국어 · Deutsch · Français · Slovenčina
A local-first coordination bus for a fleet of AI agents working in parallel — within a single repository or spread across a whole ecosystem of them. One WebSocket hub is the shared source of truth for presence, work claims, chat, task status, and resource offers: agents address each other across projects and share one plan, while file-scope claims keep the agents in any one repository from receiving overlapping live authority. Documented provider hooks and the staged Git gate enforce that authority only on their covered mutation surfaces.
See it refuse, crash and recover
python -m pip install synapse-channel && synapse demo --recoveryTwo scripted agents share one hub and one throwaway Git repository; no model or provider is called. In about 40 seconds the real hub shows that:
- the second agent's overlapping file claim is refused;
- its attempt to hand itself the first agent's task is refused;
- the first agent writes half of its change and crashes without releasing;
- while that lease is live, the second agent can neither claim nor write the file;
- when the lease runs out, the second agent claims the file under a new epoch, and the restarted first agent's release is refused;
- result verification reports the half-written file as not done;
- the second agent finishes the change, its own test passes, and the hub accepts the release.
Each step prints what the hub or the verifier answered. The run writes recovery-demo.json with the package version, both lease epochs and both verification verdicts. synapse demo without the flag runs the shorter claim, conflict, handoff and receipt story.
Watch the presentation
Watch the SYNAPSE CHANNEL presentation on YouTube (8 minutes; starts from the beginning).
New here? Read Why SYNAPSE CHANNEL — a
five-minute read on what it is, what you build on it, how it differs from the
tools next to it, and why coordination becomes the bottleneck once you run more
than one agent.
Project lineage: SYNAPSE CHANNEL dates back to September 2025.
The bus requires Python 3.11 or newer and is transport-light (websockets), hub-centric by design (one place owns presence, leases, and history), and runs entirely on the local machine. Model workers reply on-channel through any OpenAI-compatible endpoint, including a local Ollama server, with a deterministic rule-based fallback for offline use.
The bundled synapse mcp server uses the Model Context Protocol (MCP) to expose send, durable inbox, status, claim, release, handoff, and task verbs as MCP tools plus the board, agents, and resources as read-only MCP resources. Host interoperability depends on the installed host version, transport and configuration; see the exact support boundaries in the integration catalogue. The A2A HTTP surface has its separately stated partial qualification. The base runtime uses websockets on Python 3.11 or newer; adapters use their declared optional extras (pip install 'synapse-channel[mcp]'). See the MCP guide and the separately qualified authenticated HTTP profile.
Scoped execution outcomes distinguish A2A/MCP exchanges, wake transport and worker process exits from external business effects. Unknown outcomes require inquiry or operator recovery; reconnect does not automatically repeat work.
python -m pip install synapse-channel && synapse demoGet the Python package · Run the first 60 seconds · Read the quickstart
Group and Project Map
SYNAPSE CHANNEL is the coordination layer of the Agentic Coordination, Assurance and Continuity Systems group: independent projects for running AI agents as accountable engineering participants. The bus is where the agents meet, and this repository holds the canonical map of the group.
| Part of the map | Repositories and purpose |
|---|---|
| Coordination | SYNAPSE-CHANNEL, SYNAPSE-CHANNEL-FLEET and SYNAPSE-POLICY-CHECK-ACTION: the coordination bus, its multi-machine operation and its release-policy check in CI. |
| Assurance | DIRECTOR-AI, DIRECTOR-CLASS-AI, DIRECTOR-AI-CLOUD and RIGOR-FOUNDRY: grounded answers, action control, the hosted control plane and evidence-bound repository audits. |
| Continuity | REMANENTIA and REMANENTIA-PORTAL: memory that survives the session, and customer identity and entitlements. |
| Supporting tools | HushLine: command-output filtering. Emerging tools are not designed yet. |
Each project has its own development, versioning and release lifecycle; none requires the whole group. The group and project map gives every repository's function and current status and explains what each line on the schematic means.
Full-size SVG · PNG · JPG
Coordinate. Observe. Govern.
Synapse's daily promise is three explicit loops:
- Coordinate declared work and surface collisions:
synapse git-init,synapse git-claim,synapse git-claim-check --staged,synapse task, andsyn ackturn work scope, dependencies, and evidence into shared state instead of side-channel notes. - Observe the fleet from durable state:
synapse who,synapse state,synapse dashboard,synapse event-query, and observed peer rows show who is present, what is claimed, what changed, and which peer-hub facts are advisory. - Govern risky actions with evidence: policy checks, approvals, release receipts, Merkle roots, ACL surfaces, federation, and encryption-key commands make operator decisions auditable. Governance surfaces report by default; operators decide what blocks a merge, release, or cross-hub action.
- Protect the durable log at rest with optional SQLCipher page encryption for the live hub event store (plus whole-file AES-GCM envelopes for relay logs, A2A state, cursors, and archives). See SQLCipher live event store below.
What it does, surface by surface
Seven shipped coordination surfaces, each named by the command or doc that delivers it today:
- Claim before edit.
synapse git-initinstalls claim-aware Git hooks;synapse git-claimrecords an exact worktree, branch, and path scope so an overlapping claim can be refused before files diverge.
- Block unclaimed native file edits. Provider file-edit claim hooks adapt Claude Code
Edit|Write, Codex `appl
Only the beginning is shown; read the rest in the repo