Ext Ops Panel
Open dashboard
Comparison

autorouter vs MCPProxy

autorouter is an MCP server published by Webb-Ventures. Marketplaces we read that list it: 1 (Official MCP Registry). MCPProxy is an MCP server published by smart-mcp-proxy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceautorouterMCPProxy
Official MCP Registry Listed
Version: 0.2.8
Downloads/month (npm): 1 017
Downloads/week (npm): 62
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.70.0
Forks (GitHub): 62
Stars (GitHub): 390
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

autorouter vs MCPProxy
FactautorouterMCPProxy
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)390 (better)
Forks (GitHub) (differs)0 (worse)62 (better)
Last release (differs)2026-10-13Not published
Where it runs (differs)On your machine (autorouter-mcp)Not stated
Transport (differs)stdioNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/webb-ventures/autoroutergithub.com/smart-mcp-proxy/mcpproxy-go
Changes in the last 7 days (differs)10
First seen2026-10-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

autorouter

In its own words, on Official MCP Registry:

An MCP capability router: one search tool instead of every server's tool schema.

MCPProxy

In its own words, on Official MCP Registry:

Local-first MCP proxy with BM25 tool discovery, security scanning, quarantine & ~99% token savings

How to run each

autorouter As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio autorouter -- npx -y autorouter-mcp serve

MCPProxy

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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 MCPProxy publish no settings it asks for, so we do not compare settings.

What it can do: autorouter · What it can do: MCPProxy · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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