council-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | API key for xAI / Grok. | |
| KIMI_API_KEY | No | API key for Moonshot / Kimi. Providers without a key are unavailable, but the server can still run with the remaining providers. | |
| GEMINI_API_KEY | No | API key for Google Gemini. | |
| DEEPSEEK_API_KEY | No | API key for DeepSeek. DeepSeek is the default judge. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| council_deliberateA | Run multi-model deliberation: several models answer a question in parallel, then a judge synthesizes the best answer. Use for high-stakes decisions, architecture questions, debugging strategy, or any question where hallucination risk matters. |
| council_list_modelsA | List the provider/model pairs available for deliberation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one executes a deliberation, the other enumerates available models. There is no plausible way to confuse listing models with running a deliberation.
Both names use the same 'council_' prefix followed by a clear verb_noun pattern (council_deliberate, council_list_models). The convention is predictable and readable.
Two tools is thin for a server, though the domain (multi-model deliberation with a judge) is narrow enough that a discovery tool plus a single execution tool may genuinely be all that's needed. It sits at the borderline of minimal but defensible.
The surface covers the core operation and model discovery, but there is no way to inspect or retrieve prior deliberations, configure the judge/models per call, or check status of a long-running deliberation. These are notable gaps an agent could hit, though the primary workflow is usable.