Server facts
deliberation MCP Server
Project
- Author
- antonbabenko
- Repository
- github.com/antonbabenko/deliberation
- License
- Not specified
- Category
- AI Models & Agents
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 177
- Last commit
- Data as of
Tags
- code review
- consensus
- gemini
- gpt
- grok
- mcp
- multi model
- openrouter
- orchestration
- second opinion
- subagents
Overview
Development reviews in Deliberation draw on whichever GPT, Gemini, Grok, or OpenRouter providers are configured. The ask-all tool requests independent responses in parallel, while panel lists eligible providers without contacting them and ask-one targets a named member. Direct expert tools focus those reviews on architecture, plan readiness, scope, code quality, security, research, or debugging. For questions requiring a shared verdict, consensus supports provider-led review and revision rounds; consensus-step lets the host manage the process, recording its initial judgment before gathering peer opinions.
Reviews are advisory, with GPT and Gemini also able to implement changes when requested; Grok and OpenRouter remain advisory. Session persistence is disabled by default. When enabled, session-get retrieves saved opinions and verdicts, session-annotate adds notes, and session-revisit reruns the original question against the current configuration while linking the new record to its source. The local analyze tool offers configuration suggestions using debug timing data and stored agreement information as separate views, with debug logging required for timing analysis. Developers can use these workflows in Claude Code or another MCP host over stdio.
deliberation setup notes
- deliberation records stdio only; confirm a network transport upstream before planning remote access.
- deliberation has no recorded license; confirm reuse terms in its repository.