Ext Ops Panel
Open dashboard
Comparison

io.github.DiaaAj/a-mem-mcp vs io.github.Hustada/collective-memory

io.github.DiaaAj/a-mem-mcp is an MCP server published by DiaaAj. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Hustada/collective-memory is an MCP server published by Hustada. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.DiaaAj/a-mem-mcpio.github.Hustada/collective-memory
Official MCP Registry Listed
Version: 0.2.1
Downloads/month (PyPI): 445
Downloads/week (PyPI): 51
Forks (GitHub): 3
Stars (GitHub): 35
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 102
Downloads/week (npm): 19
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

io.github.DiaaAj/a-mem-mcp vs io.github.Hustada/collective-memory
Factio.github.DiaaAj/a-mem-mcpio.github.Hustada/collective-memory
Marketplaces that list it11
Stars (GitHub) (differs)35 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (a-mem)On your machine (collective-memory)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)5, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/diaaaj/a-mem-mcpgithub.com/hustada/collective-memory
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.DiaaAj/a-mem-mcp

In its own words, on Official MCP Registry:

Self-evolving memory system for AI agents

io.github.Hustada/collective-memory

In its own words, on Official MCP Registry:

MCP server for persistent, semantic memory across AI sessions

How to run each

io.github.DiaaAj/a-mem-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio a-mem-mcp -- uvx a-mem

Requires: OPENAI_API_KEY (secret)

io.github.Hustada/collective-memory As a local MCP server: npm package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio collective-memory -- npx -y collective-memory

Requires: OPENAI_API_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

Only io.github.DiaaAj/a-mem-mcp asks for

  • CHROMA_DB_PATH
  • EMBEDDING_MODEL
  • LLM_BACKEND
  • LLM_MODEL

Only io.github.Hustada/collective-memory asks for

None

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

What it can do: io.github.DiaaAj/a-mem-mcp · What it can do: io.github.Hustada/collective-memory · Compare two other plugins

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.

Where the data comes from: how the catalog is built