Gemot Deliberation Server
Run structured multi-agent deliberation—cruxes, vote clustering, and consensus—through MCP instead of ad-hoc prompt debates.
Overview
dev.gemot/gemot is a Build-phase MCP server that provides multi-agent deliberation with cruxes, vote clustering, and consensus.
What is this MCP server?
- Deliberation primitives: cruxes, vote clustering, and consensus for multi-agent runs
- Hosted remotes: streamable HTTP and SSE at gemot.dev (v0.11.0)
- No local npm package required—connect remote MCP endpoints
- GitHub source at justinstimatze/gemot for self-host or audit
- Gemot Deliberation Server version 0.11.0
- Two hosted remotes: streamable HTTP and SSE at gemot.dev
- Repository: github.com/justinstimatze/gemot
Community signal: 2 GitHub stars.
What problem does it solve?
Several agents arguing in one thread hides real disagreements and produces mushy decisions before you write code or ship.
Who is it for?
Builders orchestrating multiple agent roles who need repeatable deliberation before architecture, scope, or launch choices.
Skip if: Single-agent chats with no multi-role setup or teams that only need a straight code-generation skill.
What do I get? / Deliverables
After connecting Gemot remotes, your workflow can cluster votes, name cruxes, and reach explicit consensus artifacts agents can act on.
- Crux-focused view of disagreements between agent positions
- Vote clusters and consensus outcomes usable in downstream prompts
- Repeatable deliberation step in a multi-agent build pipeline
Recommended MCP Servers
Journey fit
Gemot fits Build when you orchestrate several agents or sub-agents and need a deliberation layer before committing to code or launches. Agent-tooling is the shelf for coordination primitives that agents invoke mid-build, distinct from one-off API integrations.
How it compares
Coordination and consensus MCP primitive, not a codebase indexer or deployment integration.
Common Questions / FAQ
Who is dev.gemot/gemot for?
It is for indie builders and small teams using multi-agent coding setups who want structured deliberation instead of unstructured debate.
When should I use dev.gemot/gemot?
Use it during Build when several agents must align on tradeoffs—architecture, scope, or priorities—before implementation or release steps.
How do I add dev.gemot/gemot to my agent?
Add the remote MCP URL https://gemot.dev/mcp (streamable HTTP) or https://gemot.dev/mcp/sse in your agent’s MCP config, then call deliberation tools from your multi-agent workflow.