collective-memory
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@collective-memoryrecall recent decisions and context"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: CogniRepo
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_summaryZero 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
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.
Parameter | Type | Required | Description |
| string | yes | The memory to store — be specific and self-contained |
| string | no | Project context (e.g., "myapp", "client-x") |
| string | no | One of: decision, milestone, context, learning, session_summary |
| string[] | no | Tags for categorization |
Returns the stored memory ID, or existing ID if deduplicated.
recall
Search memories by semantic similarity.
Parameter | Type | Required | Description |
| string | yes | Natural language search query |
| string | no | Filter to specific project |
| string | no | Filter to specific memory type |
| number | no | Max 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 myappConfiguration
Environment Variable | Default | Description |
| (required) | OpenAI API key for embeddings |
|
| Storage location |
How it works
Store: Content is embedded using OpenAI's
text-embedding-3-small(768 dimensions)Dedupe: Before storing, checks for >95% similar existing memories
Index: Stored in LanceDB, an embedded vector database
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.jsonTo visualize:
npm run dash # Opens UMAP visualization at localhost:3333License
MIT
Credits
Built by The Victor Collective.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hustada/collective-memory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server