Ai Counsel MCP Server

True deliberative consensus MCP server where AI models debate and refine positions across multiple rounds. That is what the ai counsel mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• 🎯 Two Modes: quick (single-round) or conference (multi-round debate)
• 🤖 Mixed Adapters: CLI tools (claude, codex, droid, gemini) + HTTP services (ollama, lmstudio, openrouter, nebius)
• ⚡ Auto-Convergence: Stops when opinions stabilize (saves API costs)
• 🗳️ Structured Voting: Models cast votes with confidence levels and rationale
• 🧮 Semantic Grouping: Similar vote options automatically merged (0.70+ similarity)
• 🎛️ Model-Controlled Stopping: Models decide when to stop deliberating

The tools it exposes

The server publishes 9 tools. What each one is for:

• Prerequisites — 1. Python 3.11+: python3 --version 2. At least one AI tool (optional - HTTP adapters work without CLI): - Claude CLI
• Setup — ✅ Ready to use! Server includes core dependencies plus optional convergence backends (scikit-learn, sentence-transformers) for best accuracy
• Configuration — The Configuration tool exposed by this server
• Troubleshooting — The Troubleshooting tool exposed by this server
• Examples — // NEW! Empty results include helpful diagnostics: { "type": "similar_decisions", "count": 0, "results": [], "diagnostics": { "total_decisions": 125
• Transcripts — All deliberations saved to transcripts/ with AI-generated summaries and full debate history
• Development — The Development tool exposed by this server
• Reference — The Reference tool exposed by this server
• Contributing — 1. Fork the repository 2. Create a feature branch (git checkout -b feature/your-feature) 3. Write tests first (TDD workflow) 4. Implement feature 5

What it needs from you

1. Python 3.11+: python3 --version 2. At least one AI tool (optional - HTTP adapters work without CLI): - Claude CLI: https://docs.claude.com/en/docs/claude-code/setup - Codex CLI: https://github.com/openai/codex - Droid CLI: https://github.com/Factory-AI/factory - Gemini CLI: https://github.com/google-gemini/gemini-cli

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ai Counsel's toolset — Prerequisites, Setup, Configuration and 6 more — is a fair guide to whether it matches your workflow. It is maintained by blueman82; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ai Counsel.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.