collective-memory MCP server
io.github.Hustada · Updated
MCP server for persistent, semantic memory across AI sessions
At a glance
collective-memory is an MCP server in the Dev Tools & Git category. It runs locally over stdio via `npx -y collective-memory`, and needs OPENAI_API_KEY. It scores B (70/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install collective-memory in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install collective-memory in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add collective-memory -e 'OPENAI_API_KEY=<OPENAI_API_KEY>' -- npx -y collective-memoryFill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Verify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install collective-memory in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "collective-memory": { "command": "npx", "args": [ "-y", "collective-memory" ], "env": { "OPENAI_API_KEY": "<OPENAI_API_KEY>" } } } }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install collective-memory in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "collective-memory": { "command": "npx", "args": [ "-y", "collective-memory" ], "env": { "OPENAI_API_KEY": "<OPENAI_API_KEY>" } } } }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install collective-memory in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.collective-memory] command = "npx" args = ["-y", "collective-memory"] env = { OPENAI_API_KEY = "<OPENAI_API_KEY>" }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install collective-memory in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "collective-memory": { "command": "npx", "args": [ "-y", "collective-memory" ], "env": { "OPENAI_API_KEY": "<OPENAI_API_KEY>" } } } }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install collective-memory in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "collective-memory": { "command": "npx", "args": [ "-y", "collective-memory" ], "env": { "OPENAI_API_KEY": "<OPENAI_API_KEY>" } } } }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
How to install collective-memory in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "collective-memory": { "type": "stdio", "command": "npx", "args": [ "-y", "collective-memory" ], "env": { "OPENAI_API_KEY": "<OPENAI_API_KEY>" } } } }Fill in your credentials
Replace <OPENAI_API_KEY> with your real value. Keep secrets out of any config file you commit.
Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What does collective-memory need from you?
API key — OpenAI API key for generating embeddings
OPENAI_API_KEYrequiredsecretEnvironment variableOpenAI API key for generating embeddings
Pass secrets through your shell environment rather than committing them into a config file.
What tools does collective-memory expose?
This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.
What the code can do
Read from the published package source — never executed. Parsed 7 of 7 source files.
This server can make network requests and read your environment variables.
How it was published
- No provenance attestation — there is nothing linking this published artifact to a specific source commit.
- 1 npm maintainer — a single point of compromise · last published by hustada.
Maintainer of this package and think something here is wrong? Tell us and we'll correct it.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
- Downloads at launch — The package is fetched from its registry each run unless you pin a version.
- Last commit 5 months ago — Actively maintained.
- 0 GitHub stars — Very little community usage so far.
Client compatibility
Health score
B · 70Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%83%
Last commit 152 days ago.
- Adoption20%0%
0 stars.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%100%
Package and registry entry point at the same repository.
- Packaging15%100%
Publishes a pinned version (0.1.2).
Documentation
Full READMECollective 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, orsession_summary - Zero config storage — Embedded vector database, no server required
Installation
npm install -g collective-memoryOr clone and build:
git clone https://github.com/Hustada/collective-memory.git
cd collective-memory
npm install
npm run buildSetup
1. Get an OpenAI API key
Required for embeddings. Get one at platform.openai.com.
2. Add to Claude Code
Alternatives to collective-memory
- memory-poisoning-scannerA · 83Scans agent code for untrusted input poisoning persistent cross-session memory
- memory-poisoning-scannerA · 83Scans agent code for untrusted input poisoning persistent cross-session memory
- Obsidian Semantic SearchA · 80Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.
- memory-search-mcpB · 71Memory Search MCP Server by MEOK AI Labs
Maintain collective-memory? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-hustada-collective-memory)Catalog data refreshed . Something wrong? Report it.