Ext Ops Panel
Open dashboard
Comparison

mcp2cli vs Rootz Archive

mcp2cli is a plugin bundle for AI coding tools published by myeolinmalchi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Rootz Archive is an MCP server published by rootz.global. 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
Marketplacemcp2cliRootz Archive
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.7.5
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

mcp2cli vs Rootz Archive
Factmcp2cliRootz Archive
Marketplaces that list it11
Stars (GitHub)44
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/rootz-global/rootz-archive/releases/download/v0.7.5/rootz-archive-0.7.5.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/myeolinmalchi/mcp2cligithub.com/rootz-global/rootz-archive
Changes in the last 7 days (differs)02
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

mcp2cli

In its own words, on Claude Code: claude-plugins-community:

Convert MCP servers to token-efficient CLI tools with auto-generated SKILL.md files for Claude Code agents

Rootz Archive

In its own words, on Official MCP Registry:

Search your local Claude Code archive. For continuous capture, use the Rootz Archive plugin.

How to run each

mcp2cli As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mcp2cli@claude-community

Rootz Archive

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: mcp2cli · What it can do: Rootz Archive · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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