Ext Ops Panel
Open dashboard
Comparison

mcp-server-dev vs Clize

mcp-server-dev is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). Clize is an MCP server published by clize.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacemcp-server-devClize
Claude Code: claude-plugins-official Listed
Version: not stated
Forks (GitHub): 4 390
Stars (GitHub): 40 325
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.52.0
Downloads/month (npm): 5 646
Downloads/week (npm): 734
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

mcp-server-dev vs Clize
Factmcp-server-devClize
Marketplaces that list it11
Stars (GitHub) (differs)40 325 (better)0 (worse)
Forks (GitHub) (differs)4 390 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleOn your machine (@clize/clize)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-officialgithub.com/cooldk/clize-cli
Changes in the last 7 days (differs)01
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

mcp-server-dev

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

Skills for designing and building MCP servers that work seamlessly with Claude. Guides you through deployment models (remote HTTP, MCPB, local), tool design patterns, auth, and interactive MCP apps.

Clize

In its own words, on Official MCP Registry:

Real-world actions for AI coding agents: an inbox with approval outbox, deploys, domains, payments.

How to run each

mcp-server-dev As a Claude Code plugin

Claude Code
/plugin install mcp-server-dev@claude-plugins-official

Clize As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio clize -- npx -y --package @clize/clize clize-mcp @clize/clize

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: mcp-server-dev · What it can do: Clize · Compare two other plugins

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