Ext Ops Panel
Open dashboard
Comparison

MCP Memory Graph vs Selvedge

MCP Memory Graph is an MCP server published by RetroRobAI. Marketplaces we read that list it: 1 (Official MCP Registry). Selvedge is an MCP server published by masondelan. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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 Memory GraphSelvedge
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 80
Downloads/week (PyPI): 24
Not marked · First seen
Listed
Version: 0.3.17
Downloads/month (PyPI): 1 004
Downloads/week (PyPI): 224
Forks (GitHub): 1
Stars (GitHub): 25
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 Memory Graph vs Selvedge
FactMCP Memory GraphSelvedge
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub25
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp-memory-graph)On your machine (selvedge)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle9
Licence (differs)Not statedMIT
Repository (differs)github.com/retrorobai/mcp-memory-graphgithub.com/masondelan/selvedge
Changes in the last 7 days00
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 Memory Graph

In its own words, on Official MCP Registry:

Authority-weighted memory graph for AI agents with conflict detection and semantic search.

Selvedge

In its own words, on Official MCP Registry:

Persistent decision memory for AI agents: rationale, rejected approaches, and entity history.

How to run each

MCP Memory Graph As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-memory-graph -- uvx mcp-memory-graph

Selvedge As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio selvedge -- uvx --from selvedge selvedge-server selvedge

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

The marketplaces of MCP Memory Graph publish no settings it asks for, so we do not compare settings.

What it can do: MCP Memory Graph · What it can do: Selvedge · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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