Skip to main content
Glama
Sign In
model-council-mcp-codex

model-council-mcp-codex

by tsarihan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to model-council-mcp-codex

No user-submitted related servers found.

    Related Servers

    • Roundtable MCP

      hardc0l2e
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      8 npm
      1
      MIT

    • Conclave MCP

      stephenpeters
      A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      8
      1
      MIT
    • mumo

      mumoofficial

      mumo-chat
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multi-model deliberation by sending questions to various AI models and aggregating their responses and typed cross-model reactions, facilitating agreement, challenge, and exploration for tasks like architecture review and strategy.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources