Ext Ops Panel
Open dashboard
Comparison

GitDiagram vs io.github.meta-taro/zumen

GitDiagram is an MCP server published by gitdiagram.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.meta-taro/zumen is an MCP server published by meta-taro. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceGitDiagramio.github.meta-taro/zumen
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 1 412
Stars (GitHub): 18 366
Not marked · First seen
Listed
Version: 0.6.1
Downloads/month (npm): 291
Downloads/week (npm): 291
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

GitDiagram vs io.github.meta-taro/zumen
FactGitDiagramio.github.meta-taro/zumen
Marketplaces that list it11
Stars (GitHub) (differs)18 366 (better)0 (worse)
Forks (GitHub) (differs)1 412 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (gitdiagram.com/mcp)On your machine (@metataro/zumen-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ahmedkhaleel2004/gitdiagramgithub.com/meta-taro/zumen
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)Responded 46 h agono remote endpoint we check

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

GitDiagram

In its own words, on Official MCP Registry:

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

io.github.meta-taro/zumen

In its own words, on Official MCP Registry:

AI-editable diagrams as code: draw from YAML, propose diffs a human applies, export SVG/Mermaid.

How to run each

GitDiagram As a remote MCP server

Claude Code
claude mcp add --transport http gitdiagram https://gitdiagram.com/mcp

io.github.meta-taro/zumen As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio zumen -- npx -y @metataro/zumen-mcp

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

Only GitDiagram 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

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

What it can do: GitDiagram · What it can do: io.github.meta-taro/zumen · Compare two other plugins

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