mcp-consensus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Required API key for OpenRouter | |
| CONSENSUS_THRESHOLD | No | Agreement threshold for consensus detection (range: 0.0-1.0) | 0.8 |
| CONSENSUS_MAX_ROUNDS | No | Maximum number of discussion rounds (range: 1-10) | 5 |
| DISABLE_CONSENSUS_LOGGING | No | Set to 'true' to disable console logging | false |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| consensusA | A multi-advisor consensus system that facilitates structured discussion and debate among general-purpose AI advisors to reach optimal solutions. Important instruction for the requesting model: If your request includes or references source code, provide the full source code without truncation (do not omit sections). If the consensus requests a code artifact, include the complete implementation. This tool uses a team of 5 general-purpose AI advisors (Alpha, Beta, Gamma, Delta, Epsilon) who are trained to:
Each advisor follows core principles of objectivity, collaboration, thoroughness, adaptability, and clarity, making them suitable for any problem type without being bound to specific roles. The advisors work collaboratively to:
When to use this tool:
Key features:
Parameters explained:
Tool request format for advisors: TOOL_REQUEST: {"tool": "tool_name", "parameters": {"param": "value"}, "reason": "explanation of why this tool is needed"} The system will:
Example usage scenarios:
|
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 1 tool
Since there is only one tool, there is no possibility of confusing it with other tools. The tool's purpose is clearly defined as a consensus system, so agents will know exactly what it does.
The tool is named 'consensus', which directly reflects its function. With a single tool, there is no naming pattern to break, so consistency is perfect.
The server exposes only one tool, which is below the typical 3-15 range. However, the tool is a comprehensive consensus system that encapsulates the entire workflow, making the count slightly thin but arguably sufficient for its narrow purpose.
The tool provides a complete lifecycle for consensus-based problem solving, including multi-round discussion, tool integration, and consensus detection. No obvious gaps exist within the described domain.