mnemonic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_FILE_PATH | No | Custom location for the memory file. Overrides the default path (~/.mcp-memory/memory.md on Linux/macOS or %USERPROFILE%\.mcp-memory\memory.md on Windows). |
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 |
|---|---|
| read_memoryA | Read persistent memory. Use list_sections first if unsure where info is stored, then read that section directly. |
| auto_saveA | Silently save information about me worth remembering long-term. Call this proactively during conversations when I reveal preferences, facts, corrections, or project state — don't announce you're doing it unless asked. |
| save_memoryA | Explicitly save a fact to memory when asked directly. Automatically categorizes into appropriate section. |
| update_memoryC | Find and replace existing memory. Pass exact text to find. |
| delete_memoryB | Delete something from memory. Provide a unique fragment. |
| search_memoryA | Search for specific info in memory. Uses keyword matching across all entries. |
| list_sectionsA | List all named sections in memory. Use this when you're unsure where info might be stored. |
| save_to_sectionA | Add info to a categorized section. Creates it if needed. |
| replace_sectionA | Replace ALL content in a named section. |
| tidy_memoryA | Organize standalone dated entries into appropriate sections. Use this when memory.md has many orphaned entries that could be categorized. |
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 10 tools
Most tools target distinct actions, but save_memory, auto_save, and save_to_section overlap in purpose, and read_memory/search_memory/list_sections have fuzzy boundaries without clear parameter detail. Descriptions reduce but do not eliminate confusion.
The dominant pattern is verb_noun: read_memory, save_memory, update_memory, delete_memory, search_memory, list_sections. auto_save breaks the pattern slightly, and save_to_section/replace_section use prepositions, but the overall naming style is recognizable and consistent enough.
Ten tools is a reasonable size for a memory management server. Each tool covers a distinct facet of reading, writing, organizing, searching, or maintaining persistent memory without feeling padded.
The memory domain is well covered with CRUD operations, search, section management, and maintenance. Minor gaps include no explicit 'list all memory at once' tool and no dedicated 'delete section' operation, but these can be worked around.