hindsight-memory vs io.github.sumanaddanki/suma-memory
hindsight-memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
hindsight-memory is a plugin bundle for AI coding tools published by Hindsight Team. No marketplace we read lists it any more. io.github.sumanaddanki/suma-memory is an MCP server published by sumanaddanki. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
| Marketplace |  io.github.sumanaddanki/suma-memory | |
|---|---|---|
| Community marketplace holetron-lab/fleet-memory | Removed on 2026-10-15 Version: 0.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 148 Downloads/week (npm): 8 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | hindsight-memoryno longer listed · | io.github.sumanaddanki/suma-memory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (sumapro.quadframe.work/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/holetron-lab/fleet-memory | github.com/sumanaddanki/suma-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (7 days ago) |
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 hindsight-memory
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Persistent memory system for Claude Code - seamlessly preserve context across sessions
-
Persistent local memory for Claude Code — cross-session context, semantic search, zero cloud
-
Persistent semantic memory for Claude Code. Stores knowledge in a local ChromaDB vector database and automatically retrieves relevant context on every message using Ollama bge-m3…
-
Persistent memory system for Claude Code - context compression across sessions
-
Persistent memory system for AI coding sessions — cross-tool memory sharing with hybrid search
-
Persistent long-term memory for Claude Code — wires SessionStart/UserPromptSubmit/PostToolUse hooks, MCP tools, memory skills, and the memory-review agent into a running Remnic…
What each says it does
hindsight-memory
Automatic long-term memory for Claude Code via Hindsight
io.github.sumanaddanki/suma-memory
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
How to run each
hindsight-memory
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.sumanaddanki/suma-memory As a remote MCP server
claude mcp add --transport http suma-memory https://sumapro.quadframe.work/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: SUMA_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.sumanaddanki/suma-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
The marketplaces of hindsight-memory publish no settings it asks for, so we do not compare settings.
What it can do: hindsight-memory · What it can do: io.github.sumanaddanki/suma-memory · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.