A
licenseA
qualityA
maintenanceRoutes questions to multiple AI models (local and cloud) and synthesizes their answers in individual, categorized, or deconflicted modes.
9
1
Apache 2.0
model-council-mcp-codex
by tsarihan
Related Servers
Alternatives to model-council-mcp-codex
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables running AI councils across Claude, GPT, and Gemini, synthesizing answers based on your personal taste lens, all locally without an API key.1MIT
- AlicenseAqualityBmaintenanceEnables role-based, multi-model AI orchestration by assigning specialized expert roles to a hybrid panel of local and cloud LLMs, generating unified advisory council reports for complex tasks.68 npm1MIT
- AlicenseAqualityDmaintenanceProvides access to multiple frontier LLM models (GPT, Claude, Gemini, Grok, DeepSeek) for consulting a "conclave" of AI perspectives, enabling peer-ranked evaluations and synthesized consensus answers for important decisions.81MIT
MergeLoopofficial
AlicenseAqualityCmaintenanceA host-agnostic model council that routes tasks across multiple AI workers (MCP, CLI, API) and returns one unified answer.13Apache 2.0- AlicenseAqualityDmaintenanceEnables AI assistants to create council hearings where multiple LLMs (Claude, GPT, Gemini, Grok) debate topics and synthesize verdicts with trust scores and diverse perspectives.210 npmApache 2.0
TDQS
A4.4/5.0
Scored across 9 tools
Disambiguation4/5
Most tools have clearly distinct purposes, but setup_council and configure_council both modify council configuration, and get_council_config and council_status both report council members. Descriptions clarify the boundaries, so ambiguity is low but not zero.
Naming Consistency4/5
Tool names mostly follow a verb_noun pattern (list_models, configure_council, ask_council, get_council_result, set_council_timeouts), but council_status is a noun phrase and deviates. The overall convention is consistent enough to be predictable.
Tool Count5/5
9 tools is well-scoped for a model council management server. Each tool covers a necessary part of the lifecycle: discovery, setup, configuration, synchronous/asynchronous querying, result retrieval, status, and timeout management.
Completeness5/5
The tool surface provides full lifecycle coverage for a model council: list available models, set up and configure the council, ask questions synchronously or asynchronously, retrieve results, check status, and adjust timeouts. No critical operations are missing.
Maintenance
ActivitySlowing
ResponsivenessNo issues