AI编码助手持久内存服务

Memory MCP

Persistent memory and full-text session search for AI coding assistants, exposed as an MCP server.

The problem

AI coding assistants forget everything between sessions. Architecture decisions, user preferences, project context, what you debugged last Tuesday -- gone. You re-explain the same things constantly.

Memory MCP fixes this with two capabilities:

1. Explicit memory -- save notes, decisions, patterns, and preferences that persist across sessions. Your assistant remembers what you told it.
2. Session search -- full-text search across your entire conversation history. Find that thing you discussed three weeks ago without scrolling through logs.

No database servers. No background processes. No cloud. One SQLite file on your machine.

Supported session sources

Adding a new source requires one parser file and a registry entry. See Adding a new source.

Installation

Requires Python 3.11+ with SQLite FTS5 support (included in standard Python builds).

pip install -e .

Or run directly with uv (no install needed):

uv run --directory /path/to/memory_mcp python -m memory_mcp

MCP configuration

Add to your MCP client config (e.g., ~/.claude/mcp.json or project-level .mcp.json):

With pip install:

{
  "mcpServers": {
    "memory": {
      "command": "memory-mcp"
    }
  }
}

With uv (no install):

{
  "mcpServers": {
    "memory": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/memory_mcp", "python", "-m", "memory_mcp"]
    }
  }
}

Tools

Memory (explicit knowledge store)

Sessions (historical conversation search)

Multi-machine sync (optional)

Memory MCP can sync sessions and memories across multiple machines via a self-hosted sync server. When configured, each machine pushes its local data to a central PostgreSQL database and pulls data from other machines.

Quick start

1. Deploy the sync server with PostgreSQL + systemd. See DEPLOY.md for the Proxmox/no-Docker playbook.

   Current lab shape:

   • memory-mcp app VM: FastAPI service on :8000
   • pg2026 DB VM: PostgreSQL 18 + pgvector

2. Create an API key:

   复制

   python3 -c "import secrets; print(secrets.token_hex(32))"
   

   Insert the SHA-256 hash into PostgreSQL:

   复制

   INSERT INTO users (id, name, api_key_hash, created_at)
   VALUES (gen_random_uuid(), 'austin', '<sha256-of-api-key>', now());
   

3. Configure each machine with environment variables:

   复制

   export MEMORY_MCP_SYNC_URL=http://your-server:8000
   export MEMORY_MCP_SYNC_KEY=your-secret-key
   

4. Restart memory-mcp — the sync engine starts automatically. On the first configured sync, existing rows in ~/.memory_mcp/memory.db are assigned this machine's UUID and uploaded; no separate SQLite export is needed.

How sync works

• Offline-first: all reads go to local SQLite. Sync is a background process — your tools are never blocked waiting for the network.
• Push: pending sessions and memories are POSTed to the server after each scan cycle and after each save_memory call.
• Pull: the server returns items authored by other machines since the last pull. Sessions use INSERT OR IGNORE (idempotent); memories use last-write-wins conflict resolution by updated_at.
• Machine identity: each host generates a persistent UUID on first run (~/.memory_mcp/machine_id). This UUID is the sync key.
• No env vars = local-only: if MEMORY_MCP_SYNC_URL and MEMORY_MCP_SYNC_KEY aren't set, the sync engine never starts and behavior is identical to v0.3.0.

Sync tools

How it works

On startup, Memory MCP yields its tool list to the MCP client immediately (<500 ms cold) and runs the initial session scan in a background task. The embedding model loads lazily on the first semantic search call — keyword search and saved memories work without it. Subsequent startups skip files whose mtime hasn't changed.

• Database location: ~/.memory_mcp/memory.db (override with MEMORY_MCP_DB env var)
• Session sources: auto-detected from standard locations (extend with MEMORY_MCP_SOURCES env var, format: type:path;type:path)
• Indexing: incremental by file mtime, parallelized across 8 threads
• Search: FTS5 with BM25 ranking, prefix matching, phrase support; optional vector search via sqlite-vec + fastembed (BAAI/bge-small-en-v1.5) when semantic=true is passed
• Startup: non-blocking — heavy work (scan, model load, vector backfill) runs after the server is already responding to tool calls

Adding a new session source

1. Create memory_mcp/parsers/your_source.py implementing the SessionParser protocol:
   • source_type: str attribute
   • parse_file(path: str) -> ParsedSession | None method
2. Register it in memory_mcp/parsers/__init__.py
3. Add directory detection in memory_mcp/config.py

See parsers/claude_code.py or parsers/omp.py for examples.

Testing

python tests/test_e2e.py        # end-to-end: spawns server, exercises all 10 tools
python tests/test_startup.py    # startup contract: cold Popen -> tools/list under 1.5s

test_e2e.py starts the MCP server as a subprocess, exercises all 10 tools over the stdio protocol, and asserts tool responses. test_startup.py enforces the v0.3.0 startup contract — if an eager import or pre-yield blocking call regresses startup speed, it fails immediately. Both use throwaway databases so your real data is untouched.

Architecture

memory_mcp/
  server.py        # FastMCP entry point, lifespan yields fast then runs scan + sync in background
  readiness.py     # Lazy embedder + scan/backfill coordination
  config.py        # Auto-detects session dirs, DB path, sync settings
  db.py            # SQLite + FTS5 + sqlite-vec schema, all queries, sync triggers
  embeddings.py    # Lazy fastembed wrapper (BAAI/bge-small-en-v1.5)
  scanner.py       # Walks session dirs, dispatches to parsers, parallel indexing
  machine_id.py    # Persistent machine UUID for cross-machine sync
  client.py        # HTTP client for sync server (stdlib urllib, zero-dependency)
  sync_engine.py   # Background push/pull sync loop
  parsers/
    base.py        # ParsedSession / ParsedMessage dataclasses, SessionParser protocol
    claude_code.py # Claude Code JSONL parser (merges streamed assistant blocks)
    claude_history.py # Claude Code history.jsonl parser (one file, many sessions)
    omp.py         # OMP JSONL parser
    opencode.py    # OpenCode SQLite parser (reads DB directly, read-only)
  tools/
    memory.py      # save_memory, search_memory, list_memories, delete_memory
    sessions.py    # list_sessions, get_session, search_sessions, refresh_sessions
hosted/
  server.py        # FastAPI sync server (REST API)
  models.py        # SQLAlchemy models (PostgreSQL + pgvector)
  auth.py          # Bearer API key authentication

License

MIT