Ext Ops Panel
Open dashboard
Comparison

GhostPaw Grimoire vs Mnemoverse Memory

GhostPaw Grimoire is an MCP server published by GhostPawJS. Marketplaces we read that list it: 1 (Official MCP Registry). Mnemoverse Memory is an MCP server published by mnemoverse. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
MarketplaceGhostPaw GrimoireMnemoverse Memory
Official MCP Registry Listed
Version: 0.7.1
Downloads/month (npm): 2 384
Downloads/week (npm): 678
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.17.1
Downloads/month (npm): 1 590
Downloads/week (npm): 594
Forks (GitHub): 5
Stars (GitHub): 28
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.17.1
Downloads/month (npm): 1 590
Downloads/week (npm): 594
Forks (GitHub): 5
Stars (GitHub): 28
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

GhostPaw Grimoire vs Mnemoverse Memory
FactGhostPaw GrimoireMnemoverse Memory
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)28 (better)
Forks (GitHub) (differs)1 (worse)5 (better)
Last release (differs)2026-11-05 (better)2026-11-05 (worse)
Where it runs (differs)On your machine (@ghostpaw/grimoire)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 02, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/ghostpawjs/grimoiregithub.com/mnemoverse/mcp-memory-server
Changes in the last 7 days22
First seen (differs)2026-10-242026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 h ago, requires authentication

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

GhostPaw Grimoire

In its own words, on Official MCP Registry:

Local procedural knowledge with spells, notes, and revision history.

Mnemoverse Memory

In its own words, on Official MCP Registry:

Hosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcp

How to run each

GhostPaw Grimoire As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio grimoire -- npx -y @ghostpaw/grimoire mcp

Mnemoverse Memory As a remote MCP server

Claude Code
claude mcp add --transport http mcp-memory-server https://mcp.mnemoverse.com/mcp

Requires: MNEMOVERSE_API_KEY (secret)

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

Only Mnemoverse Memory 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

Only GhostPaw Grimoire asks for

  • GHOSTPAW_GRIMOIRE_DB
  • GHOSTPAW_GRIMOIRE_GIT_DIR
  • GHOSTPAW_GRIMOIRE_ROOT

Only Mnemoverse Memory asks for

  • MNEMOVERSE_API_KEY (secret)
  • MNEMOVERSE_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: GhostPaw Grimoire · What it can do: Mnemoverse Memory · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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