memory-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_DATA_DIR | No | Directory for memory database files | Platform-specific (macOS: ~/Library/Application Support/memory-mcp/data, Linux: ~/.local/share/memory-mcp/data, Windows: %APPDATA%\memory-mcp\data) |
| MEMORY_CACHE_DIR | No | Cache directory for embedding model | System default |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_storeC | Store a memory. kind must be one of: preference, project, workflow, knowledge, summary. |
| memory_searchA | Search memories by semantic similarity and keywords. Returns ranked results. |
| memory_listB | List memories with optional filters. Ordered by creation date descending. |
| memory_updateB | Update an existing memory's content, tags, or priority. |
| memory_deleteC | Delete a memory by ID. |
| memory_statsA | Get memory system statistics: total count, breakdown by kind and project. |
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 6 tools
Each tool has a clearly distinct purpose: delete by ID, list with filters, search by similarity/keywords, get stats, store new, update existing. No overlap.
All tools follow a consistent 'memory_verb' pattern in snake_case, making the operation immediately clear.
6 tools is well-scoped for a memory system, covering core operations without unnecessary bloat.
Covers CRUD (store, list, search, update, delete) plus stats. Minor gap: no explicit get-by-id, but list/search likely return full memory objects.