MCP Tools DirectoryAbout this integration
Consult other LLMs as tools — ask them, compare their answers, synthesize a conclusion.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.14.0
- Package
- model-council-mcp
- Last compatibility test
- Not independently tested
Connect your agent
model-council-mcpPublisher documentation and the executable manifest were reviewed. Each local stdio process uses configured provider endpoints and API keys; HTTP team mode is a separate connection with network allowlisting rather than per-person identity. Package execution, model calls, provider behavior, costs, and security were not tested.
Capabilities: Ask one or multiple configured language-model endpoints, Run multi-round cross-review and revision workflows, Inspect configured council members and probe model identifiers
Connected profiles
Additional details
io.github.Totti0135/model-council
Source ↗ · Checked 2026-09-170.14.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17model-council-mcp
Source ↗ · Checked 2026-09-200.14.0
Source ↗ · Checked 2026-09-20The documented stdio mode launches one server process per client with configured provider keys and handles model requests without repeated user authorization.
Source ↗ · Checked 2026-09-20Configured council members use provider API keys paired with their base URLs and wire formats.
Source ↗ · Checked 2026-09-20Run model-council-mcp through uvx as a stdio server and pass provider endpoint, key, model, and format variables.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20