Collective Memory

io.github.HustadaPublished by GitHub account Hustadav0.1.2Updated Oct 27, 2026

MCP server for persistent, semantic memory across AI sessions

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

Local MCP server that gives an assistant persistent semantic memory, letting it store notes, decisions and learnings and recall them later by meaning.

What you can do
  • Store a memory with optional project, type and tags, with near-duplicates skipped automatically
  • Search stored memories by natural-language query, filtered by project or type and capped by a result limit
  • Organize memories by project and classify them as decision, milestone, context, learning or session_summary
  • Keep everything in a local embedded vector database, with export and a local visualization dashboard available from the command line
When to use it
Useful when you want an assistant to carry context across separate sessions — remembering decisions, milestones and lessons per project — and to retrieve them later by describing what you are looking for rather than exact keywords.
Requirements
Runs as a local stdio process, installed globally from npm or built from source with Node.js. Requires an OpenAI API key in the OPENAI_API_KEY environment variable for generating embeddings, so network access to OpenAI is needed. Storage defaults to a local data directory and can be changed with COLLECTIVE_MEMORY_PATH.
Before you install
Every stored memory and every search query is sent to OpenAI to be embedded, so avoid putting secrets or sensitive material into memories. The OPENAI_API_KEY is a billable credential and must be supplied in the server configuration. Memories are written to local disk and persist between sessions, so review what gets stored.

Installation

In SourceWeft

  1. Open Collective Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

bash
npm install -g collective-memory

Or clone and build:

bash
git clone https://github.com/Hustada/collective-memory.gitcd collective-memorynpm installnpm 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:

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

Or if installed from source:

json
{  "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:

markdown
## 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:

bash
# Store a memorycollective-memory remember --content "Decided to use PostgreSQL for the auth service"
# Search memoriescollective-memory recall --query "database decisions" --limit 5
# Pipe content from stdinecho "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:

bash
npm run export  # Outputs to viz/memories.json

To visualize:

bash
npm run dash    # Opens UMAP visualization at localhost:3333

License

MIT

Credits

Built by The Victor Collective.

Source: README.md at commit 550c3c4

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Memory integrations