Skip to content
MCP server

Synod Council

MCP server for durable two-agent deliberation with worktree isolation and peer review

Pricing
Open source
Platforms
CLI, API, self-hosted
Version
0.2.0
Listing updated
today

Similar MCP servers

About Synod Council

Synod Council is an open-source MCP server for agent tooling. It is available on CLI, API and self-hosted.

The README describes Synod as a way for two AI agents to reach decisions together and make code changes without one simply approving whatever the other produces. Each deliberation runs through stages such as planning, cross-review, synthesis and ratification, and session state is kept in SQLite so a stopped run can be inspected afterwards.

Code work happens in a separate git worktree and branch per session, and the README says agents do not push to main; a human approval step comes before anything is published. Validation checks run after implementation, and failures are sent back to the implementing agent for a bounded number of retries.

The project is exposed as a Python library, an HTTP server and an MCP server over stdio. According to the README it was extracted from a personal infrastructure setup, and support for more than two participants is listed as future work.

What it does

Symmetric two-agent protocol
Either agent can start a deliberation, and the protocol gives neither side a privileged role.
Durable SQLite session state
Each deliberation stage is recorded so a crashed run leaves an inspectable trail.
Isolated git worktrees
Each session gets its own worktree and branch, keeping code changes separate from main.
Peer review and ratification
Agents review each other's plans, and a rejection triggers explicit reconciliation.
Validation with bounded retries
Post-implementation checks send failures back to the implementing agent before a human sees them.
MCP, HTTP and library access
The README lists an MCP server over stdio, an HTTP endpoint and a Python library interface.

Good for

  • Having two coding agents settle an architecture choice before code is written
  • Running implementation work in isolated branches with a human approval gate
  • Inspecting how an automated multi-agent decision was reached after a failed run
  • Calling deliberation from an MCP-capable client such as Claude Desktop or Cursor

Pricing

Open source

Free and open source under MIT.

Synod Council FAQ

What license is Synod released under?

The README links to an MIT license.

How many agents can take part in a deliberation?

The design is intentionally two-agent; the README says N-participant support is on the roadmap.

How is the MCP server started?

The README gives the command synod-mcp, which uses stdio transport.

Can agents push code directly to main?

The README says agents never push to main and that a human-facing approval step comes before publishing.

Is Synod Council free?

Yes. Synod Council is open source, so you can use and self-host it for free.

What are the best alternatives to Synod Council?

The closest alternatives to Synod Council are Synapbus, DeskPartner, Agent Memory MCP, Seamless and mcp-memory-rs.

Where this comes from

  • Description: written from the project's README and its MCP Registry entry.

How AIPoweredBot checks servers