Ext Ops Panel
Open dashboard
Comparison

io.eraser/eraser vs CodePic

io.eraser/eraser is an MCP server published by eraser.io. Marketplaces we read that list it: 1 (Official MCP Registry). CodePic is an MCP server published by abelce. 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
Marketplaceio.eraser/eraserCodePic
Official MCP Registry Listed
Version: 0.2.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
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

io.eraser/eraser vs CodePic
Factio.eraser/eraserCodePic
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.eraser.io/api/mcp)Remote server (codepic.cc/api/mcp/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/abelce/codepic-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agoResponded 4 days ago

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

io.eraser/eraser

In its own words, on Official MCP Registry:

Generate, edit, and manage Eraser diagrams and docs with AI.

CodePic

In its own words, on Official MCP Registry:

AI agent draws editable hand-drawn diagrams (flowchart, ER, architecture) via MCP, not static images

How to run each

io.eraser/eraser As a remote MCP server

Claude Code
claude mcp add --transport http eraser https://app.eraser.io/api/mcp

CodePic As a remote MCP server

Claude Code
claude mcp add --transport http codepic https://codepic.cc/api/mcp/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Both endpoints responded at the last daily 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: io.eraser/eraser · What it can do: CodePic · 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