Mcp Rubber Duck

Created By
nesquikm4 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
4 months ago
Updated At
4 months ago
Author Name
nesquikm
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago