Back to Browse

Collective Memory MCP Server

Developer ToolsUse Caution4.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for persistent, semantic memory across AI sessions

About

MCP server for persistent, semantic memory across AI sessions

Security Report

4.2
Use Caution4.2High Risk

Collective Memory is a well-architected MCP server for semantic memory storage with appropriate authentication and reasonable permission scope. The codebase demonstrates good security practices with environment-based credential handling, input validation via Zod schemas, and no malicious patterns. Minor code quality issues around error handling and logging do not significantly impact security posture. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

HTTP Network Access

Connects to external APIs or services over the internet.

What You'll Need

Set these up before or after installing:

OpenAI API key for generating embeddingsRequired

Environment variable: OPENAI_API_KEY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-hustada-collective-memory": {
      "env": {
        "OPENAI_API_KEY": "your-openai-api-key-here"
      },
      "args": [
        "-y",
        "collective-memory"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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.

ParameterTypeRequiredDescription
contentstringyesThe memory to store — be specific and self-contained
projectstringnoProject context (e.g., "myapp", "client-x")
typestringnoOne of: decision, milestone, context, learning, session_summary
tagsstring[]noTags for categorization

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

recall

Search memories by semantic similarity.

ParameterTypeRequiredDescription
querystringyesNatural language search query
projectstringnoFilter to specific project
typestringnoFilter to specific memory type
limitnumbernoMax results (default: 10)

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

Environment VariableDefaultDescription
OPENAI_API_KEY(required)OpenAI API key for embeddings
COLLECTIVE_MEMORY_PATH~/.collective-memory/dataStorage location

How it works

  1. Store: Content is embedded using OpenAI's text-embedding-3-small (768 dimensions)
  2. Dedupe: Before storing, checks for >95% similar existing memories
  3. Index: Stored in LanceDB, an embedded vector database
  4. Search: Queries are embedded and matched via cosine similarity

Data

Memories are stored locally at ~/.collective-memory/data (or COLLECTIVE_MEMORY_PATH). It's a LanceDB database — portable, no server process.

To export memories:

npm run export  # Outputs to viz/memories.json

To visualize:

npm run dash    # Opens UMAP visualization at localhost:3333

License

MIT

Credits

Built by The Victor Collective.

Reviews

No reviews yet

Be the first to review this server!