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
Synod Council
Overview
Description from the maker (original English)
Durable symmetric deliberation between two AI agents, with isolated worktrees and peer review.
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: –
- Transport:
- 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.
The maker has not listed install details in the registry. See the maker’s README below.
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 naruminho, 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 32661 servers in this category
- Published to the registry more recently than 30% of the other 32661 servers in this category
- Basic checks equal to or better than 100% of the other 32661 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 Synod Council 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.2.0) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Claude Checkpoint MCP
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
Claude Checkpoint MCP
by daniel-munoz
MCP server that checkpoints Claude Code session context to survive crashes and token limits
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.
Synod
Durable, symmetric deliberation between two AI agents — with isolated git worktrees, peer review, automated validation, and an explicit approval workflow.
Synod started life as the "council" inside a personal AI infrastructure where two autonomous agents (an orchestrator and an executor) needed to make *real* decisions and *real* code changes together — without one of them silently becoming the other's rubber stamp.
Why
Most multi-agent frameworks are orchestration theater: one agent calls another as a tool and calls the output "collaboration". Synod is built around a different premise — two agents that are peers by construction:
- Symmetric protocol — either agent can initiate; the protocol has no privileged side.
- Identity contract — every prompt re-establishes who the agent is, so a weak or distracted model can't drift into answering *as* its peer.
- Bias-resistant synthesis — the synthesizer for each problem is chosen by hashing the problem text, not by who spoke first.
- Durable state — every session lives in SQLite with explicit stages (
plan,review,synthesize,ratify, ...). A crashed run leaves an inspectable trail, not a mystery. - Code changes land through worktrees — each session gets its own git worktree and branch. Agents never push to
main; a human-facing approval step stands between "looks done" and "published". - Validation with remediation — checks run after implementation, failures go back to the implementing agent with bounded retries before a human ever sees it.
Install
pipx install synod-councilOr from source:
git clone https://github.com/naruminho/synod-councilcd synod && pip install .
Usage
Library
from synod.deliberation import Deliberator, Store, HTTPAdapteradapters = { "Alice": HTTPAdapter("Alice", "http://127.0.0.1:9001/ask"), "Bob": HTTPAdapter("Bob", "http://127.0.0.1:9002/ask"), } synod = Deliberator(adapters, Store("council.db")) result = synod.run("Should we use SQLite or Postgres for this workload?", initiator="Alice") print(result.decision, result.confidence, result.status) # consensus | reconciled
MCP server
Synod ships an MCP server so any MCP-capable client (Claude Desktop, Claude Code, Cursor, ...) can start a deliberation:
synod-mcp # stdio transportAdd it to your client config and ask your agents to *deliberate* instead of guessing.
HTTP server
synod-server --port 8790curl -X POST http://127.0.0.1:8790/run -d '{"problem": "...", "initiator": "Alice"}'
How a deliberation flows
plan (parallel) → cross-review (parallel) → synthesis → [ratification → reconciliation?]If reviewers raise unresolved blockers, or confidence lands below 0.7, the candidate decision goes to ratification by the non-synthesizing peer; a rejection forces explicit reconciliation instead of silent consensus.
Status
Extracted and battle-tested from a production personal infrastructure where it has been deciding architecture and shipping code since 2026. The two-agent design is intentional; N-participant support is on the roadmap.
License
MIT