Ext Ops Panel
Open dashboard
Comparison

LLM Router vs io.github.nesquikm/rubber-duck

LLM Router is a plugin bundle for AI coding tools published by ypollak2. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-15. 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

Where each is published
MarketplaceLLM Routerio.github.nesquikm/rubber-duck
Community marketplace ypollak2/llm-router Listed
Version: 16.0.0
Forks (GitHub): 17
Stars (GitHub): 129
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.18.0
Downloads/month (npm): 2 459
Downloads/week (npm): 987
Forks (GitHub): 24
Stars (GitHub): 181
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): 181
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

LLM Router vs io.github.nesquikm/rubber-duck
FactLLM Routerio.github.nesquikm/rubber-duck
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)129 (worse)181 (better)
Forks (GitHub) (differs)17 (worse)24 (better)
Last release (differs)Not published2026-11-02
Where it runs (differs)On your machine (llm-routing)On your machine (mcp-rubber-duck)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 3
Hooks it runs (differs)16Not published
Parts of the bundle (differs)17Not a bundle
LicenceMITMIT
Repository (differs)github.com/ypollak2/llm-routergithub.com/nesquikm/mcp-rubber-duck
Changes in the last 7 days (differs)20
First seen (differs)2026-11-112026-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

LLM Router

In its own words, on Community GitHub marketplaces:

Route text, image, video, and audio tasks to 20+ AI providers with smart routing, budget control, and multi-step orchestration

io.github.nesquikm/rubber-duck

In its own words, on Official MCP Registry:

Bridge to multiple LLMs and CLI agents: councils, debates, voting, and more

How to run each

LLM Router As a Claude Code plugin

Claude Code
/plugin marketplace add ypollak2/llm-router
/plugin install llm-router@ypollak2

io.github.nesquikm/rubber-duck As a local MCP server: npm package

Claude Code
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-duck

Requires: 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

The marketplaces of LLM Router publish no settings it asks for, so we do not compare settings.

What it can do: LLM Router · What it can do: io.github.nesquikm/rubber-duck · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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.

Where the data comes from: how the catalog is built