Ext Ops Panel
Open dashboard
Comparison

Context7 vs Graphmem

Context7 is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Graphmem is an MCP server published by sonic182. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceContext7Graphmem
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.11.0
Downloads/month (npm): 1 436
Downloads/week (npm): 1 060
Forks (GitHub): 0
Stars (GitHub): 8
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

Context7 vs Graphmem
FactContext7Graphmem
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub8
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.context7.com/mcp)On your machine (@sonic182/graphmem)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/sonic182/graphmem
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

Context7

In its own words, on Docker MCP Catalog:

Pull up-to-date, version-specific documentation and code examples for any library or framework straight into your prompt.

Graphmem

In its own words, on Official MCP Registry:

Shared local memory for coding agents: SQLite, semantic recall, linked entities, code navigation.

How to run each

Context7

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: CONTEXT7_API_KEY (secret)

Graphmem As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio graphmem -- npx -y @sonic182/graphmem

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 Graphmem publish no settings it asks for, so we do not compare settings.

What it can do: Context7 · What it can do: Graphmem · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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