Agent Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_MEMORY_ROOT | No | Path to store memories. Default is ~/.agents/memories |
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 |
|---|---|
| create_memoryC | Create a new global or repo-scoped memory. |
| read_memoryC | Read a single global or repo-scoped memory. |
| read_memoriesC | Read global memories and memories for the provided repo. |
| update_memoryC | Update an existing global or repo-scoped memory. |
| delete_memoryB | Delete a global or repo-scoped memory. |
| list_memoriesD | List memory metadata. |
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 distinct purpose: creating, deleting, listing metadata, reading multiple, reading single, and updating memories. No overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_memory, list_memories). The plural/singular distinction for read_memories vs read_memory is appropriate.
6 tools is a well-scoped set covering full CRUD plus list and batch read operations. Not too few or too many.
The set provides complete lifecycle management for memories: create, read (single and batch), update, delete, and list metadata. No obvious gaps.