Mcp Rubber Duck

Created By
nesquikm3 months ago
Query multiple LLMs in parallel from AI coding tools. Ask a question to OpenAI, Gemini, Groq, or any OpenAI-compatible API — and CLI agents like Claude Code, Codex, and Gemini CLI — then compare answers, run consensus votes, structured debates, and judge evaluations. Rubber duck debugging, but the ducks talk back.
Overview

Rubber duck debugging, but the ducks talk back. An MCP server that bridges to multiple LLMs so you can get different perspectives without leaving your editor.

Features

  • Multi-provider querying — Ask OpenAI, Gemini, Groq, Together AI, Ollama, or any OpenAI-compatible API in parallel
  • CLI agent integration — Spawn Claude Code, Codex, Gemini CLI, Grok, and Aider as "ducks" with full codebase access
  • Duck Council — Query all providers simultaneously and compare responses side by side
  • Consensus voting — Have ducks vote on the best approach, with confidence scores
  • Structured debates — Ducks argue for and against, then a judge picks the winner
  • Conversations — Maintain chat context across multiple messages
  • MCP Bridge — Ducks can use external MCP tools (web search, file access, etc.)
  • Health monitoring — Automatic failover when a provider goes down
  • Security controls — Rate limiting, token constraints, pattern blocking, PII redaction
  • Usage analytics — Track requests, tokens, and estimated costs per provider
  • Interactive UIs — Rich HTML panels for comparison, voting, and debate visualization

Installation

npx mcp-rubber-duck

Also available via Docker and the official MCP Registry.

Server Config

{
  "mcpServers": {
    "rubber-duck": {
      "command": "mcp-rubber-duck",
      "env": {
        "MCP_SERVER": "true",
        "OPENAI_API_KEY": "<YOUR_OPENAI_KEY>",
        "GEMINI_API_KEY": "<YOUR_GEMINI_KEY>",
        "DEFAULT_PROVIDER": "openai"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
nesquikm
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Scratchpad Mcp
@MikePressure

scratchpad-mcp is an MCP server that gives AI agents persistent, token-efficient storage. It solves a specific waste problem: agents constantly re-read files they've already seen, re-summarize documents they've already processed, and re-load context they've already understood. Every one of those round-trips burns tokens for no new information. This server fixes that with eight tools designed around how agents actually work: Versioned writes. write_file automatically versions every write and keeps the 10 most recent versions per file. Storage is append-only on success and atomic on failure partial writes can't corrupt state. Structured diffs. read_file accepts a since_version parameter and returns a JSON line-diff against that prior version instead of the full content. Agents that have already seen v1 can ask "what changed in v3?" and get a small structured payload they can reason about, not the entire file again. Append-only logs. append_log and read_log give agents an event-stream they can replay. Cursor-based pagination (since_entry + last_entry_id + has_more) means an agent can checkpoint where it left off and resume cheaply. On-demand summaries. summarize_file calls Claude Haiku to summarize files over ~2000 estimated tokens. Summaries are cached per file version, so repeat calls on an unchanged file cost nothing. The threshold is enforced server-side you can't accidentally pay to summarize something small. Per-agent isolation. Every operation is scoped by an agent_id parameter, so one server instance can serve many agents without leaking state between them. Storage limits. 1 MB per file write, 64 KB per log entry, 1000 files / 100k log entries / 100 MB total per agent sane multi-tenant guardrails out of the box. Backed by a single SQLite file (Postgres migration is on the roadmap). All SQL is parameterized, paths are validated against a strict allowlist, and the security model is documented honestly it's safe for one-user-per-process deployments today, and the V2 plan derives agent_id from the caller's API key for true multi-tenancy. Build agents that remember what they've already seen.

6 hours ago
Fomox402

7 hours ago