MCP Tools DirectoryAbout this integration
Bridge to multiple LLMs and CLI agents: councils, debates, voting, and more
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 1.18.0
- Package
- mcp-rubber-duck
- Last compatibility test
- Not independently tested
Connect your agent
mcp-rubber-duckPublisher README and npm manifest reviewed from pinned captures. Package, model providers, CLI agents, and bridged servers were not invoked. Model outputs and provider compatibility were not independently verified.
Capabilities: Query and compare configured model providers, Maintain multi-turn provider conversations, Run councils, votes, judging, refinement, and debates, Track provider health and usage, Bridge configured providers to external MCP servers
Connected profiles
Additional details
io.github.nesquikm/rubber-duck
Source ↗ · Checked 2026-09-171.18.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mcp-rubber-duck
Source ↗ · Checked 2026-09-191.20.8
Source ↗ · Checked 2026-09-19Publisher documents an npm stdio server started with npx and persistent conversation, health, usage, failover, provider, and MCP-bridge services.
Source ↗ · Checked 2026-09-19Prerequisites vary by backend: an HTTP provider API key or a locally installed CLI coding agent. This mixed provider mechanism is outside one native authentication class.
Source ↗ · Checked 2026-09-19The server is launched locally with npx mcp-rubber-duck and obtains provider selection, API keys, CLI-agent enablement, and bridge settings from environment or config files.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19