Ext Ops Panel
Open dashboard
Comparison

nagato-mcp-tools vs @agent-deck/cli

nagato-mcp-tools is an MCP server published by Chromoforge. Marketplaces we read that list it: 1 (PyPI (MCP servers)). @agent-deck/cli is an MCP server published by @agent-deck. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
Marketplacenagato-mcp-tools@agent-deck/cli
PyPI (MCP servers) Listed
Version: 0.2.3
Downloads/month (PyPI): 914
Downloads/week (PyPI): 778
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
npm registry (MCP servers) Not listed Listed
Version: 2.4.0
Downloads/month (npm): 1 529
Downloads/week (npm): 341
Forks (GitHub): 0
Stars (GitHub): 4
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

nagato-mcp-tools vs @agent-deck/cli
Factnagato-mcp-tools@agent-deck/cli
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)4 (better)
Forks (GitHub)00
Last release (differs)Not published2026-11-01
Where it runs (differs)On your machine (nagato-mcp-tools)On your machine (@agent-deck/cli)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/chromoforge/nagato-mcp-toolsgithub.com/not-so-fat/agent_deck
Changes in the last 7 days00
First seen2026-10-122026-10-12

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

nagato-mcp-tools

In its own words, on PyPI (MCP servers):

Agent-First MCP Toolkit -- code search, editing, execution, and analysis tools for any MCP client.

@agent-deck/cli

In its own words, on npm registry (MCP servers):

Local MCP proxy — decks of tools, keys, and self-improving playbooks

How to run each

nagato-mcp-tools

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

@agent-deck/cli

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

Neither one's marketplaces publish the settings it asks for.

What it can do: nagato-mcp-tools · What it can do: @agent-deck/cli · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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