Ext Ops Panel
Open dashboard
Comparison

mcp2cli vs 3DAssets.dev

mcp2cli is a plugin bundle for AI coding tools published by myeolinmalchi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 3DAssets.dev is an MCP server published by 3dassets.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
Marketplacemcp2cli3DAssets.dev
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: 1.0.1
Downloads/month (npm): 222
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
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 3DAssets.dev
Factmcp2cli3DAssets.dev
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (3dassets.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/myeolinmalchi/mcp2cligithub.com/3dassets-dev/3dassets
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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

3DAssets.dev

In its own words, on Official MCP Registry:

Search and download free CC0 GLB models and game packs, and submit new ones on a user behalf.

How to run each

mcp2cli As a Claude Code plugin

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

3DAssets.dev As a remote MCP server

Claude Code
claude mcp add --transport http catalogue https://3dassets.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: THREEDASSETS_API_KEY (secret), Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only 3DAssets.dev has a remote endpoint we check. How we check endpoints

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

What it can do: mcp2cli · What it can do: 3DAssets.dev · 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