mcp-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_MEMORY_DATA_DIR | No | Where memories are stored on disk | ~/.mcp-memory/ |
| MCP_MEMORY_MAX_RESULTS | No | Default number of recall results | 10 |
| MCP_MEMORY_DEFAULT_PROJECT | No | Default project scope | global |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Store a memory for later recall. Content is embedded for semantic search. |
| recallA | Search memories by semantic similarity. Returns the most relevant stored memories. |
| forgetC | Delete stored memories. Specify at least one filter criterion. |
| list_memoriesA | Browse and list stored memories with optional filtering. |
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 distinct purpose: remember stores, recall searches semantically, list_memories browses with filtering, and forget deletes. There is no overlap or ambiguity.
Most tools use single verb names (remember, recall, forget), but 'list_memories' breaks the pattern with a verb_noun style. The naming is clear but not fully consistent.
With 4 tools covering create, read (two retrieval methods), and delete, the count is well-scoped for a memory server. No tools feel redundant or missing.
The set covers create, read (list and search), and delete, but lacks an update operation. There is no way to modify an existing memory, which is a notable gap for a typical CRUD lifecycle.