Ext Ops Panel
Open dashboard
Comparison

metro vs io.github.portel-dev/ncp

metro is a plugin bundle for AI coding tools published by Bonustrack. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.portel-dev/ncp is an MCP server published by portel-dev. 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
Marketplacemetroio.github.portel-dev/ncp
Community marketplace bonustrack/metro Listed
Version: 0.9.19
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.3
Downloads/month (npm): 2 163
Downloads/week (npm): 81
Forks (GitHub): 9
Stars (GitHub): 100
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

metro vs io.github.portel-dev/ncp
Factmetroio.github.portel-dev/ncp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub100
Forks (GitHub) (differs)No figure on GitHub9
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@portel/ncp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Hooks it runs (differs)2Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bonustrack/metrogithub.com/portel-dev/ncp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

metro

In its own words, on Community GitHub marketplaces:

Every connector on this box as its own MCP server through metro's local relay, the orchestrator guard, and the standing rules loaded at session start.

io.github.portel-dev/ncp

In its own words, on Official MCP Registry:

N-to-1 MCP Orchestration. Unified gateway for multiple MCP servers with intelligent tool discovery.

How to run each

metro As a Claude Code plugin

Claude Code
/plugin marketplace add bonustrack/metro
/plugin install metro@metro

io.github.portel-dev/ncp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ncp -- npx -y @portel/ncp

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

What it can do: metro · What it can do: io.github.portel-dev/ncp · 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. 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