A
licenseNot graded
qualityC
maintenanceMulti-model AI council MCP server that lets multiple LLMs debate, critique, and vote on questions to reach a consensus, with automatic failover and hot-swap of models during debates.
MIT
Model Council
by Totti0135
Related Servers
Alternatives to Model Council
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that enables users to query, compare, and synthesize responses from multiple local and cloud LLMs simultaneously using existing subscriptions. It provides tools for parallel model evaluation, consensus polling with an LLM-as-judge, and response synthesis across different model providers.815 npm16MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables an AI orchestrator to convene a council of other AIs via their CLIs, deliberate, and synthesize consensus.1 npmGPL 3.0
- AlicenseAqualityAmaintenanceBlind multi-model councils with anonymous LLM seats and direct 1:1 chat as a local MCP server. Enables asking one question to get independent answers from multiple model CLIs, then blind scoring and reveal.17AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agents to conduct multi-LLM roundtable discussions, returning structured common, divergent, and unique perspectives.MIT
- AlicenseAqualityBmaintenanceMCP server that reduces confirmation bias in LLMs by orchestrating structured debates between asymmetric context sessions.13MIT
TDQS
A4.6/5.0
Scored across 6 tools
Disambiguation4/5
The tools are mostly distinct: ask targets one member, ask_all targets many, revise drives an existing discussion forward, and list_council/probe_models serve different inspection purposes. Some adjacency exists between ask_all and revise, and between list_council and probe_models, but the descriptions explicitly separate these cases.
Naming Consistency3/5
Naming is mixed: bare verbs like ask and revise, a phrasal verb like ask_all, verb_noun pairs like list_council and probe_models, and a noun-phrase tool name in revision_prompt. The names are still readable and domain-grouped, but they do not follow one consistent pattern.
Tool Count5/5
Six tools is well-scoped for a model-council server: one-member queries, multi-member discussion, on-demand revision, prompt construction, roster inspection, and endpoint probing all earn their place. There is no filler and no glaring redundancy.
Completeness5/5
The core workflow is fully covered: ask a single member, ask the whole council, revise iteratively, build prompts for an external seat, list members, and probe available model ids. Configuration of members is intentionally operator-side, so no create/update/delete tools are expected.
Maintenance
ActivityMaintained
ResponsivenessNo issues