Ext Ops Panel
Open dashboard
Comparison

neuralscape vs io.github.gitmem-dev/gitmem

neuralscape is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.

neuralscape is a plugin bundle for AI coding tools published by Ehfaz Rezwan. No marketplace we read lists it any more. io.github.gitmem-dev/gitmem is an MCP server published by gitmem-dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceneuralscapeio.github.gitmem-dev/gitmem
Community marketplace ehfazrezwan/neuralscape Removed on 2026-10-21
Version: 2.9.2
Forks (GitHub): 1
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.1
Downloads/month (npm): 1 924
Downloads/week (npm): 133
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.11.2
Downloads/month (npm): 1 924
Downloads/week (npm): 133
Forks (GitHub): 1
Stars (GitHub): 9
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

neuralscape vs io.github.gitmem-dev/gitmem
Factneuralscapeno longer listed · io.github.gitmem-dev/gitmem
Marketplaces that list it (differs)02
Stars (GitHub) (differs)69
Forks (GitHub)11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (ns.siliconinja.dev/mcp)On your machine (gitmem-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)7Not published
Parts of the bundle (differs)20Not a bundle
LicenceMITMIT
Repository (differs)github.com/ehfazrezwan/neuralscapegithub.com/gitmem-dev/gitmem
Changes in the last 7 days (differs)40
First seen (differs)2026-10-162026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of neuralscape

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • mempenny

    Keep Claude Code auto-memory lean. Triage (delete/archive/distill) memory files without losing forward-looking truth. Pairs with caveman.

    by marcelopaniza · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • memory-toolkit

    Session memory lifecycle for Claude Code. Structured handoffs between sessions, workstreams to switch context without losing it, background watcher (Haiku) that captures decisions…

    by IlyaGorsky · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • mem0

    Connect Mem0 to Claude to give your agent persistent memory across sessions. Claude can store user preferences, project context, and conversation history, then search, update, or…

    by mem0ai · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • engram io.github.tstockham96/engram

    Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.

    by tstockham96 · MCP server

    Listed on: Official MCP Registry, Claude Code: claude-plugins-community · Describes nearly the same job

  • mengram

    Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal…

    by Ali Baizhanov · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • everos

    EverOS memory for Claude Code - automatic recall, capture and session seal against a local EverOS server.

    by EverMind AI · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

neuralscape

In its own words, on Community GitHub marketplaces:

Persistent agentic memory for Claude (Code + Cowork). In Claude Code, hooks auto-capture conversations and recall context on session start; in Cowork (no plugin hooks), the cross-platform skills (recall/remember/save-session/project/ingest) drive memory via the bundled OAuth MCP connector. The ingest skill loads files/folders/pasted context (Markdown/HTML/PDF/MS-Office). Exposes 14 MCP tools.

io.github.gitmem-dev/gitmem

In its own words, on Official MCP Registry:

Persistent institutional memory for AI coding agents. Memory that compounds.

How to run each

neuralscape

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

io.github.gitmem-dev/gitmem As a local MCP server: npm package

Claude Code
claude mcp add --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --transport stdio gitmem -- npx -y gitmem-mcp

Requires: SUPABASE_SERVICE_ROLE_KEY (secret)

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

What it can do: neuralscape · What it can do: io.github.gitmem-dev/gitmem · 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. 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