memory-mcp vs Zihin
memory-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
memory-mcp is a plugin bundle for AI coding tools published by Michael Denyer. No marketplace we read lists it any more. Zihin is an MCP server published by zihin.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  Zihin | |
|---|---|---|
| Community marketplace michael-denyer/memory-mcp | Removed on 2026-10-28 Version: 0.8.0 Forks (GitHub): 2 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.2 Downloads/month (npm): 593 Downloads/week (npm): 43 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 | memory-mcpno longer listed · | Zihin |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 14 | 0 |
| Forks (GitHub) (differs) | 2 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (llm.zihin.ai/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) | 17 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/michael-denyer/memory-mcp | github.com/zihin-ai/zihin-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
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 memory-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
-
Encrypted long-term memory shared across your AI assistants (Claude, ChatGPT, Perplexity).
-
One shared, persistent memory across AI agents and systems, with semantic recall and live updates.
-
Local-first agent memory for Claude Code — recall, remember, ambient capture.
-
Graph-vector memory for AI assistants using FalkorDB and Qdrant
-
Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.
What each says it does
memory-mcp
Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.
Zihin
Chat with your Zihin.ai agents, list them and load platform skills from any MCP client.
How to run each
memory-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Zihin As a remote MCP server
claude mcp add --transport http zihin https://llm.zihin.ai/mcp --header "X-Api-Key: <YOUR_X_API_KEY>"Requires: ZIHIN_API_KEY (secret), X-Api-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Zihin 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 memory-mcp publish no settings it asks for, so we do not compare settings.
What it can do: memory-mcp · What it can do: Zihin · 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.