This server enables intelligent searching and navigation of Claude Code memory files, allowing you to efficiently retrieve relevant context without loading every memory into the context window.
search_memory: Perform ranked keyword searches across all memory file bodies, with scoring bonuses for title and description matches. Supports an optional limit parameter to control the number of results.
get_memory: Retrieve the complete contents of a specific memory file by its name (without the .md extension), useful for loading only what you need on demand.
list_memories: List all available memory files, with an optional filter by type (user, feedback, project, or reference) to narrow results.
find_related: Discover memories linked to or from a given memory file via [[wikilinks]], enabling traversal of connected context across the memory graph.
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., "@claude-memory-search-mcp search memories for 'database migration'"
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.
MCP server that searches and links across Claude Code memory files.
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
Tool | Args | Description |
|
| Ranked keyword search across all memory bodies. Bonuses for title and description hits. |
|
| Fetch the full body of one memory by file name (no |
|
| List every memory, optionally filtered by type. |
|
| Return memories linked from or to a given memory via |
git clone https://github.com/yangchoi/claude-memory-search-mcp.git
cd claude-memory-search-mcp
npm install
npm run buildnpx -y github:yangchoi/claude-memory-search-mcpSlower on first invocation (npx fetches and builds), then cached.
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__*.
> 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
...MIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Universal memory for AI agents and tools. Save, organize and search context anywhere.
Persistent memory and knowledge graph for AI assistants — keyword + vector + graph search.
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/yangchoi/claude-memory-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server