Queries multiple OpenAI-compatible APIs and CLI agents for debugging perspectives, comparisons, debates, and consensus.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag โ we're steadily working through the catalog.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Rubber Duck.
ask_duckAsk a single question to a specific LLM provider
chat_with_duckConversation with context maintained across messages
clear_conversationsClear all conversation history
list_ducksList configured providers and health status
list_modelsList available models for providers
compare_ducksAsk the same question to multiple providers simultaneously
The nesquikm/mcp-rubber-duck MCP server gives an MCP client access to multiple AI providers through one server. It can send prompts to OpenAI-compatible HTTP endpoints or invoke supported command-line coding agents as local processes. Supported HTTP provider examples include OpenAI, Gemini, Anthropic-compatible endpoints, Groq, Together AI, Perplexity, Azure OpenAI, Ollama, LM Studio, and custom endpoints. CLI options include Claude Code, Codex, Gemini CLI, Grok CLI, Aider, and custom agents.
The main use case is getting additional perspectives while debugging, reviewing a design, or comparing possible answers. A single request can target one provider, while comparison and council tools can query several configured providers. Voting, judging, iteration, and debate tools support more structured multi-model workflows.
The server communicates directly with configured provider APIs rather than relying on MCP sampling. Conversations can retain context across messages, and conversation history can be cleared through a dedicated tool. Provider listings expose configured ducks and health status, while model listing reports available models. Automatic failover can use another provider when the primary provider fails.
Usage tracking records requests and tokens and provides estimated costs. The server also includes MCP Bridge functionality, allowing ducks to access connected MCP servers when that feature is enabled. Bridge access has per-server approval controls, with tools for viewing pending requests and approving or denying them.
Four tools can expose MCP Apps interfaces in clients that support them: comparisons, voting, debates, and usage statistics. Clients without MCP Apps support receive plain text results instead. The project also documents vision input for models that support images, reusable MCP prompt templates, and configurable guardrails such as rate limiting, token limits, pattern blocking, and PII redaction.
Install Node.js 20 or later, then install the package globally with npm install -g mcp-rubber-duck, or run it through npx. Source installation uses the repository, npm install, npm run build, and npm start.
The nesquikm/mcp-rubber-duck MCP server can read settings from a .env file or config/config.json. HTTP providers can be configured with variables such as OPENAI_API_KEY, GEMINI_API_KEY, and GROQ_API_KEY. DEFAULT_PROVIDER and DEFAULT_TEMPERATURE set default request behavior, while LOG_LEVEL controls logging. Set MCP_SERVER=true for MCP server mode and MCP_BRIDGE_ENABLED to enable bridge access. Custom providers and CLI agents use the documented CUSTOM_{NAME}_* and CLI_{AGENT}_ENABLED configuration patterns.
At least one HTTP provider API key or one locally installed CLI coding agent is needed. CLI providers must also be configured according to their individual setup requirements.
The server does not provide a single universal model backend; results depend on the configured HTTP endpoints or installed CLI agents. HTTP use generally requires the user's provider credentials, and provider usage may incur separate costs. Local CLI agents must already be installed and available to the process. Interactive HTML panels depend on MCP Apps support in the client, although equivalent plain text output remains available.
The nesquikm/mcp-rubber-duck MCP server's README excerpt does not state a license. It also does not identify a minimum provider configuration beyond requiring either an API key or a local CLI agent.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/nesquikm-mcp-rubber-duck)<a href="https://allmcps.com/mcp/nesquikm-mcp-rubber-duck"><img src="https://allmcps.com/api/badge/nesquikm-mcp-rubber-duck?style=directory" alt="MCP Rubber Duck on AllMCPs" /></a>