memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key. Required for real Claude calls (used by the `remember` MCP tool and the CLI). | |
| AGENT_MEMORY_MODEL | No | The model used for extraction, decisions and answers. Defaults to Haiku 5.5. | claude-haiku-5-5 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Store what the user said about themselves. Facts that replace older ones (a new city, a new job) are recorded as updates and the old fact is kept as history. |
| recallB | Find memories relevant to a query. Each result says whether it is current or no longer true. |
| list_memoriesA | Everything remembered about a user (current facts only unless include_history is true). |
| list_entitiesB | People, pets, places and organizations in the user's memory, with how many memories mention each. |
| forgetA | Permanently delete one memory (for example when the user asks to be forgotten). |
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 5 tools
Each tool has a clearly distinct role: remember writes, recall does query-based retrieval, list_memories enumerates all facts, list_entities enumerates people/places, and forget deletes. The recall vs. list_memories boundary (search vs. full listing) is explicitly spelled out in the descriptions, leaving no real overlap.
All names are imperative lowercase verbs, which gives a readable, predictable style. However, the pattern is not strictly verb_noun: remember/recall/forget omit the object while list_memories/list_entities include one, a minor inconsistency but not confusing.
Five tools is well-scoped for a personal memory store: one write, three read shapes, and one delete. Every tool earns its place with no redundant or speculative operations.
The lifecycle is essentially covered: remember implicitly handles updates with history, and forget handles deletion. Minor gaps exist, such as bulk deletion of all of a user's data (beyond one memory at a time) and no way to remove or merge entities explicitly.