claude-memory-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_MEMORY_DIR | No | Path to the Claude memory directory. Optional; defaults to ~/.claude/projects/<user-home>/memory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoryA | Search across memory files by keyword. Returns ranked hits with file name, score, matched terms, type, and description. |
| get_memoryA | Fetch the full body of a memory file by its name (without .md). |
| list_memoriesA | List all memory files. Optionally filter by type (user/feedback/project/reference). |
| find_relatedA | Find memories linked from or to a given memory via [[wikilinks]]. Returns related memory names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: find_related for wikilink navigation, get_memory for full content retrieval, list_memories for enumeration with filtering, and search_memory for keyword search. No overlap in functionality.
All tool names follow the consistent snake_case verb_noun pattern (find_related, get_memory, list_memories, search_memory). No deviations or mixed conventions.
4 tools is well-scoped for a memory search server. Each tool serves a distinct need (listing, retrieval, search, link navigation) without unnecessary redundancy or gaps.
The set covers core read/search operations for a memory system. However, it lacks write operations (create, update, delete), which may be intentional given the 'search' focus, but slightly limits completeness for full lifecycle management.