klayoutclaw vs io.github.neo4j-contrib/mcp-neo4j-data-modeling
klayoutclaw is a plugin bundle for AI coding tools published by caidish. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.neo4j-contrib/mcp-neo4j-data-modeling is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-11-04. 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
| Marketplace |  io.github.neo4j-contrib/mcp-neo4j-data-modeling | |
|---|---|---|
| Community marketplace caidish/klayoutclaw | Listed Version: 0.6.0 Forks (GitHub): 7 Stars (GitHub): 40 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (PyPI): 2 484 Downloads/week (PyPI): 115 Forks (GitHub): 263 Stars (GitHub): 989 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3c72de00df50 Forks (GitHub): 263 Pulls (Docker Hub): 24 643 Stars (Docker Hub): 1 Stars (GitHub): 989 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
| Fact | klayoutclaw | io.github.neo4j-contrib/mcp-neo4j-data-modeling |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 40 (worse) | 989 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 24 643 |
| Forks (GitHub) (differs) | 7 (worse) | 263 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (127.0.0.1/mcp) | On your machine (mcp-neo4j-data-modeling) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | Not published | 16 |
| Environment variables it asks for (differs) | Not published | 6, secrets among them: 0 |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/caidish/klayoutclaw | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no 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
klayoutclaw
Control KLayout from AI agents via MCP — geometry, display, image overlay, visual capture, nanodevice flake detection, GDS alignment, and routing skills
io.github.neo4j-contrib/mcp-neo4j-data-modeling
A simple Neo4j MCP server for creating graph data models.
How to run each
klayoutclaw As a Claude Code plugin
/plugin marketplace add caidish/klayoutclaw
/plugin install klayoutclaw@klayoutclawio.github.neo4j-contrib/mcp-neo4j-data-modeling As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-neo4j-data-modeling -- uvx mcp-neo4j-data-modelingCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only klayoutclaw has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of klayoutclaw publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of klayoutclaw publish no settings it asks for, so we do not compare settings.
What it can do: klayoutclaw · What it can do: io.github.neo4j-contrib/mcp-neo4j-data-modeling · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.