Deliberation
Related Servers
Alternatives to Deliberation
- AlicenseNot gradedqualityDmaintenanceThe simplest way to bridge and collaborate across AI Agent sessions like Claude Code, Codex, Gemini, or Cursor. It allows your agents to combine their strengths to solve your most difficult tasks without leaving their current context.24 npm69MIT
- AlicenseAqualityDmaintenanceMulti-AI Consensus Tool: Query multiple AI models in parallel, synthesize responses for better accuracy, and reduce AI bias through ensemble decision-making.133MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server enabling Claude to consult Codex (GPT-5.x) mid-task for second opinions, plan/diff review, brainstorming, and codebase exploration via structured debates and permission-controlled interactions.2MIT
- AlicenseNot gradedqualityBmaintenanceMCP servers that let Claude Code delegate to other coding CLIs (Copilot, Codex, Gemini) for cross-model second opinions, structured reviews, and multi-engine consultations.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that gives any AI coding tool a structured second opinion from another AI provider.6 npmMIT
- AlicenseBqualityAmaintenanceMCP server orchestrating API-first cross-review between Claude, ChatGPT Codex, Gemini, DeepSeek, Grok, and Perplexity with unanimous convergence gates.28594 npmApache 2.0
- AlicenseAqualityDmaintenanceMCP server orchestrating local CLI agents (Claude Code, OpenAI Codex, Google Gemini) for cross-validation, second opinions, and persona-driven prompting.18MIT

polydevofficial
AlicenseNot gradedqualityDmaintenanceQuery GPT-5, Claude, Gemini, and Grok simultaneously through one MCP server for multi-model AI perspectives in your coding agents.316 npmMIT
TDQS
Scored across 20 tools
Many tools overlap in purpose: ask-all and persona tools (architect, debugger, etc.) all fan out to providers, differing only by persona; ask-one duplicates ask-gpt/ask-gemini/ask-grok/ask-openrouter. The detailed descriptions help, but the sheer number of near-identical actions creates ambiguity for an agent.
Naming is inconsistent: some tools use verb-first hyphenated names (ask-all, session-get) while others are noun personas (architect, debugger) or single verbs (analyze). There's no uniform pattern for verbs, nouns, or hyphenation, making the set feel ad hoc.
20 tools is high and largely redundant. The specific provider tools (ask-gpt, ask-gemini, etc.) and the many persona tools (architect, plan-reviewer, etc.) could easily be consolidated into ask-one and ask-all with a persona parameter, reducing the surface without losing capability.
The tool set covers the deliberation lifecycle well: asking for opinions (ask-all, ask-one, personas), reaching consensus (consensus, consensus-step), session persistence (session-annotate, session-get, session-revisit), and performance analysis (analyze). Minor gaps like listing all sessions are not critical, so completeness is strong.