Memory MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| dataDirectory | No | Directory for storing memory data files | ./memory-server/memory-data |
| defaultTTLMinutes | No | Default TTL for short-term memory in minutes | 30 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_short_term_memoryC | Store data in short-term memory for a session |
| get_short_term_memoryC | Retrieve data from short-term memory |
| set_long_term_memoryC | Store user demographics, contact details, or preferences |
| get_long_term_memoryC | Retrieve long-term memory for a user |
| add_episodic_memoryC | Add a new episodic memory (past experience or event) |
| get_episodic_memoryC | Retrieve episodic memories for a user |
| search_episodic_memoryC | Search episodic memories by content |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memory_summary | Generate a comprehensive memory summary for a user |
| personalization_insights | Get personalization insights based on user memories |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: add vs. get vs. search for episodic memory, get vs. set for long-term and short-term memory. No ambiguity exists between tools, as they target specific memory types and operations.
All tools follow a consistent verb_noun pattern with underscores (e.g., add_episodic_memory, get_long_term_memory). The naming is predictable and uniform across all seven tools.
With 7 tools, the server is well-scoped for memory management, covering episodic, long-term, and short-term memory with appropriate operations. Each tool earns its place without feeling excessive or insufficient.
The toolset provides good coverage for memory operations, including CRUD-like actions (add/get/set) and search. A minor gap exists in not having update or delete operations for memories, but agents can likely work around this by re-setting or ignoring outdated entries.