Local AI MCP vs io.github.nesquikm/rubber-duck
Local AI MCP is an MCP server published by TMHSDigital. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.nesquikm/rubber-duck is an MCP server published by nesquikm. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Local AI MCP |  io.github.nesquikm/rubber-duck |
|---|---|---|
| Official MCP Registry | Listed Version: 0.6.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.18.0 Downloads/month (npm): 2 459 Downloads/week (npm): 987 Forks (GitHub): 24 Stars (GitHub): 180 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.20.14 Downloads/month (npm): 2 459 Downloads/week (npm): 987 Forks (GitHub): 24 Stars (GitHub): 180 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Local AI MCP | io.github.nesquikm/rubber-duck |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 180 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 24 (better) |
| Last release (differs) | 2026-11-03 (better) | 2026-11-02 (worse) |
| Where it runs (differs) | On your machine (@tmhs/local-ai-mcp) | On your machine (mcp-rubber-duck) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 3 | 4, secrets among them: 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/tmhsdigital/local-ai-mcp | github.com/nesquikm/mcp-rubber-duck |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Local AI MCP
Run, fit, and route work to local LLMs (Ollama, LM Studio, llama.cpp, MLX, vLLM, and more).
io.github.nesquikm/rubber-duck
Bridge to multiple LLMs and CLI agents: councils, debates, voting, and more
How to run each
Local AI MCP As a local MCP server: npm package
claude mcp add --env "MOONSHOT_API_KEY=<YOUR_MOONSHOT_API_KEY>" --env "OPENAI_COMPAT_API_KEY=<YOUR_OPENAI_COMPAT_API_KEY>" --env "VLLM_API_KEY=<YOUR_VLLM_API_KEY>" --transport stdio local-ai-mcp -- npx -y @tmhs/local-ai-mcpRequires: MOONSHOT_API_KEY (secret), OPENAI_COMPAT_API_KEY (secret), VLLM_API_KEY (secret)
io.github.nesquikm/rubber-duck As a local MCP server: npm package
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "GROQ_API_KEY=<YOUR_GROQ_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio rubber-duck -- npx -y mcp-rubber-duckRequires: GEMINI_API_KEY (secret), GROQ_API_KEY (secret), OPENAI_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Local AI MCP asks for
DOCKER_MODEL_RUNNER_HOSTFOUNDRY_LOCAL_HOSTLLAMACPP_HOSTLMSTUDIO_HOSTLOCAL_AI_ALLOW_HOSTED_FALLBACKLOCAL_AI_BENCHMARK_CACHELOCAL_AI_DISABLELOCAL_AI_DISABLE_NETWORK_SEARCHLOCAL_AI_PROVIDERSMLX_HOSTMOONSHOT_API_KEY (secret)MOONSHOT_HOST
Show the remaining 5
OLLAMA_HOSTOPENAI_COMPAT_API_KEY (secret)OPENAI_COMPAT_HOSTVLLM_API_KEY (secret)VLLM_HOST
Only io.github.nesquikm/rubber-duck asks for
DEFAULT_PROVIDERGEMINI_API_KEY (secret)GROQ_API_KEY (secret)OPENAI_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Local AI MCP · What it can do: io.github.nesquikm/rubber-duck · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.