AiAkiv Memory vs TeamMemory
AiAkiv Memory is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
AiAkiv Memory is a plugin bundle for AI coding tools published by OnMinimum. No marketplace we read lists it any more. TeamMemory is an MCP server published by ysydhc. 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 |  TeamMemory | |
|---|---|---|
| Community marketplace aiakiv/aiakiv-plugins | Removed on 2026-10-15 Version: 0.4.24 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Downloads/month (PyPI): 128 Downloads/week (PyPI): 13 Forks (GitHub): 0 Stars (GitHub): 1 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 | AiAkiv Memoryno longer listed · | TeamMemory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.aiakiv.com/mcp) | On your machine (team_memory) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aiakiv/aiakiv-plugins | github.com/ysydhc/team_memory |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-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 AiAkiv Memory
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.
-
Universal memory for AI agents and tools. Save, organize and search context anywhere.
-
One shared, persistent memory across AI agents and systems, with semantic recall and live updates.
-
The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes
-
membase ai.membase/membase
Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.
-
agent-memory-hardened
Persistent memory for AI agents: remember facts, learn from experience, and track entities across sessions.
What each says it does
AiAkiv Memory
Long-term memory for AI agents: save and recall conversation knowledge as a knowledge graph (MemoryWeft), via the hosted AiAkiv MCP server.
TeamMemory
Team experience database - let AI accumulate, retrieve and apply team knowledge across chats.
How to run each
AiAkiv Memory
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
TeamMemory As a local MCP server: PyPI package
claude mcp add --env "DATABASE_URL=<YOUR_DATABASE_URL>" --transport stdio team-memory -- uvx team_memoryRequires: DATABASE_URL (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 AiAkiv Memory publish no settings it asks for, so we do not compare settings.
What it can do: AiAkiv Memory · What it can do: TeamMemory · 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.