Skip to main content
Glama
slmnsrf

Councly MCP Server

by slmnsrf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Councly MCP Server

No user-submitted related servers found.

    Related Servers

    • Roundtable MCP

      hardc0l2e
      A
      license
      A
      quality
      B
      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

    • Amicus

      BourbonDog
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables multi-model LLM council reviews and parallel sidecar conversations within Claude, allowing Claude to orchestrate structured reviews from various AI models and fold their responses back into the session.
      745 npm
      2
      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
    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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: councly_hearing creates and runs a council hearing, while councly_status checks the status or retrieves results of an existing hearing. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the desired action.

    Naming Consistency5/5

    Both tools follow a consistent naming pattern with the prefix 'councly_' followed by a descriptive action (hearing, status). This verb_noun style is uniform and predictable, aiding in tool identification and usage without confusion.

    Tool Count2/5

    With only 2 tools, the server feels thin for its apparent scope of facilitating multi-LLM debates and status tracking. While the tools cover creation and status checking, the domain suggests potential gaps (e.g., no tool for listing hearings, modifying settings, or handling errors beyond status retrieval), making the count insufficient for comprehensive coverage.

    Completeness2/5

    The tool surface is significantly incomplete for the server's purpose. It lacks operations such as listing past hearings, canceling or deleting hearings, configuring hearing parameters beyond defaults, or managing user settings. This forces agents into dead ends for common workflows, like reviewing multiple past hearings or adjusting debate parameters.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources