MCP.Market

Collective Memory MCP server

by Hustada·io.github.Hustada/collective-memory·v0.1.2

MCP server for persistent, semantic memory across AI sessions

B72/100grade B
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

0 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed Collective Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Collective Memory tools (2)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • recall

    Search collective memory. Use at session start, when switching context, when referencing past work.

  • remember

    Persist important context to collective memory. Use after decisions, completed work, architectural choices, status changes. Be specific and self-contained.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 121 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Collective Memory compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 38% of 48,255 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
29
more than 16% of 12,191 servers with a package

What its tools let an agent do: 2 read

Install Collective Memory in Claude Code, Cursor or VS Code

Runs npx -y collective-memory on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add collective-memory -- npx -y collective-memory
Add to Cursor

What the publisher says

From the Collective Memory repository's README, as published. We do not edit it. Read it on GitHub

Collective Memory

MCP server for persistent, semantic memory across AI sessions. Store context, decisions, and learnings — recall them later with natural language search.

Why

AI assistants forget everything between sessions. Collective Memory fixes that. Store what matters, search by meaning, build context that compounds.

Features

  • Semantic search — Find memories by meaning, not keywords (OpenAI embeddings + LanceDB)
  • Automatic deduplication — Won't store near-duplicates (>95% similarity)
  • Project scoping — Organize memories by project
  • Type classification — Categorize as decision, milestone, context, learning, or session_summary
  • Zero config storage — Embedded vector database, no server required

Installation

npm install -g collective-memory

Or clone and build:

git clone https://github.com/Hustada/collective-memory.git
cd collective-memory
npm install
npm run build

Setup

1. Get an OpenAI API key

Required for embeddings. Get one at platform.openai.com.

2. Add to Claude Code

Add to ~/.claude/settings.json under mcpServers:

{
  "mcpServers": {
    "collective-memory": {
      "type": "stdio",
      "command": "npx",
      "args": ["collective-memory"],
      "env": {
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}

Or if installed from source:

{
  "mcpServers": {
    "collective-memory": {
      "type": "stdio",
      "command": "node",
      "args": ["/path/to/collective-memory/dist/index.js"],
      "env": {
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}

3. Add usage instructions to CLAUDE.md

Add to your global ~/.claude/CLAUDE.md:

## Memory

Collective Memory is active. Two tools:

- `remember(content, project?, type?, tags?)` — Persist important context
- `recall(query, project?, type?, limit?)` — Search memory

**On session start**: Run `recall("recent decisions and context")` to load relevant memory.

When to remember: after decisions, milestones, completed work, learned patterns.
When to recall: session start, context switches, referencing past work.

Types: decision, milestone, context, learning, session_summary.

Tools

remember

Store a memory with semantic embedding.

Returns the stored memory ID, or existing ID if deduplicated.

recall

Search memories by semantic similarity.

Returns array of matching memories with similarity scores.

CLI

Also usable from command line:

# Store a memory
collective-memory remember --content "Decided to use PostgreSQL for the auth service"

# Search memories
collective-memory recall --query "database decisions" --limit 5

# Pipe content from stdin
echo "Long content here" | collective-memory remember --content-stdin --project myapp

Configuration

How it works

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Collective Memory: common questions

Is Collective Memory MCP server safe?
Mostly: it is graded B (72/100). Read the Collective Memory safety report
How do I install Collective Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Collective Memory need an API key?
Yes. The registry entry asks for OPENAI_API_KEY.
Is Collective Memory maintained?
The last commit was 159 days ago (2026-05-29). The latest release is v0.1.2.
What can I use instead of Collective Memory?
Servers from other publishers that do the same job: Deja Vu MCP server, State Memory MCP server and Knowl MCP server.
How does Collective Memory compare with other MCP servers?
safety score 72/100 (higher than 38% of 48,255 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Collective Memory

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A