claude-memory-search-mcp

MCP server that searches and links across Claude Code memory files.

Why

Claude Code's auto-memory directory grows large quickly (100+ files in my setup). Loading every memory into context defeats the point of having them — and the auto-loaded MEMORY.md only carries a 150-char hook per entry. This server lets Claude:

• search by keyword across every memory body, not just titles,

• filter by type (user / feedback / project / reference),

• fetch a single memory in full only when needed,

• traverse [[wikilinks]] to pull related context on demand.

In short: stop trying to hold the whole memory in the window. Index it, then pull what you need.

Related MCP server: claude-kb

Tools

Install

From source (recommended for Claude Code MCP config)

git clone https://github.com/yangchoi/claude-memory-search-mcp.git
cd claude-memory-search-mcp
npm install
npm run build

Run directly via npx (no local clone)

npx -y github:yangchoi/claude-memory-search-mcp

Slower on first invocation (npx fetches and builds), then cached.

Configure in Claude Code

Add to your Claude Code MCP config (~/.claude/settings.json or project .mcp.json):

{
  "mcpServers": {
    "memory-search": {
      "command": "node",
      "args": ["/absolute/path/to/claude-memory-search-mcp/dist/index.js"],
      "env": {
        "CLAUDE_MEMORY_DIR": "/Users/you/.claude/projects/<your-project-id>/memory"
      }
    }
  }
}

CLAUDE_MEMORY_DIR is optional — by default the server derives the path from $HOME (e.g. /Users/jane → ~/.claude/projects/-Users-jane/memory on macOS, /home/jane → ~/.claude/projects/-home-jane/memory on Linux). Set it explicitly if your memory lives elsewhere.

Restart Claude Code. The four tools above will appear under mcp__memory-search__*.

Example

> search_memory query="database migration"
[42] backend-project-notes (project)
  matches: database, migration
  Postgres migration patterns and rollback strategy
[18] team-conventions (reference)
  matches: migration
  ...

License

MIT