# Synod Council

> Synod Council is an open-source MCP server for agent tooling. MCP server for durable two-agent deliberation with worktree isolation and peer review. It is available on CLI, API and self-hosted.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, API, self-hosted
- **Repository:** https://github.com/naruminho/synod-council
- **MCP Registry name:** io.github.naruminho/synod-council
- **Categories:** [agent tooling](https://ai-powered.com/categories/agent-tooling)
- **Listing updated:** 2026-11-18

## About

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.

## Features

- **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

## 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.

## Alternatives

- [Synapbus](https://ai-powered.com/mcp/synapbus): Synapbus is an open-source MCP server for agent tooling.
- [DeskPartner](https://ai-powered.com/mcp/deskpartner): DeskPartner is an open-source MCP server for agent tooling.
- [Agent Memory MCP](https://ai-powered.com/mcp/agent-memory-mcp): Agent Memory MCP is an open-source MCP server for knowledge and memory.
- [Seamless](https://ai-powered.com/mcp/seamless): Seamless is an open-source MCP server for agent tooling.
- [mcp-memory-rs](https://ai-powered.com/mcp/mcp-memory-rs): mcp-memory-rs is an open-source MCP server for knowledge and memory.

---
Source: https://ai-powered.com/mcp/synod-council
