Skip to main content
Glama
tsarihan

model-council-mcp

by tsarihan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to model-council-mcp

No user-submitted related servers found.

    Related Servers

    • Delia

      zbrdc
      F
      license
      A
      quality
      Not graded
      maintenance
      Routes AI tasks to appropriate local LLM models (quick, coder, MoE, thinking) with automatic model selection, multi-backend support (Ollama, llama.cpp, Gemini), and parallel processing capabilities.
      9
      1
      -

    • cognition-wheel

      Hormold
      A
      license
      A
      quality
      D
      maintenance
      Enables querying multiple AI models in parallel (Claude, Gemini, O3) and synthesizing their responses using anonymous analysis to reduce bias, providing a comprehensive answer.
      1
      45 npm
      193
      MIT

    • Zen MCP Server

      salvadorthebrown
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Orchestrates multiple AI models (Gemini, OpenAI, Claude, local models) within a single conversation context, enabling collaborative workflows like multi-model code reviews, consensus building, and CLI-to-CLI bridging for specialized tasks.
      -

    • Salyut

      XenaRathon
      A
      license
      Not graded
      quality
      B
      maintenance
      Fans out queries to multiple independent free LLMs from different providers and returns their answers side by side, enabling sanity-checking of decisions or getting multiple perspectives during coding sessions.
      GPL 3.0
    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.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct operation: model discovery, configuration updates, synchronous query, async query, result retrieval, config retrieval, environment status, initial setup, and timeout management. The only potential overlap between setup_council and configure_council is clearly differentiated by their descriptions (tiers vs. council composition).

    Naming Consistency4/5

    Tools follow a consistent snake_case convention with mostly verb_noun patterns (list_models, ask_council, get_council_config). Minor deviations like council_status (noun_noun) and setup_council (compound verb) are still predictable and do not hinder usability.

    Tool Count5/5

    At 9 tools, the server is well-scoped for a model council management domain. Each tool earns its place, covering discovery, setup, configuration, querying, and maintenance without unnecessary bloat.

    Completeness5/5

    The tool set covers the full lifecycle: listing models, setting up with tiers, fine-tuning configuration, synchronous and asynchronous ask, result retrieval, config/status readouts, and timeout adjustment. No critical gaps or dead ends are apparent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources