MCP Memory Service
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
| PYTHONPATH | No | Python module search path | /app |
| PYTHONUNBUFFERED | No | Disable Python output buffering | 1 |
| MCP_MEMORY_FORCE_CPU | No | Force CPU-only mode (0 or 1) | 0 |
| SIMILARITY_THRESHOLD | No | Threshold for similarity search (0.0 to 1.0) | 0.7 |
| MAX_RESULTS_PER_QUERY | No | Maximum number of results returned per query | 10 |
| MCP_MEMORY_CHROMA_PATH | No | Path to ChromaDB storage directory | /app/chroma_db |
| MCP_MEMORY_BACKUPS_PATH | No | Path to backups storage directory | /app/backups |
| PYTORCH_ENABLE_MPS_FALLBACK | No | Enable MPS fallback for Apple Silicon (0 or 1) | 1 |
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 |
|---|---|
| store_memoryC | Store new information with optional tags |
| retrieve_memoryC | Find relevant memories based on query |
| search_by_tagC | Search memories by tags |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: retrieve_memory finds memories based on content queries, search_by_tag filters by tags, and store_memory creates new entries. There is no overlap or ambiguity between these three operations.
All tools follow a consistent verb_noun pattern (retrieve_memory, search_by_tag, store_memory) with snake_case throughout. The naming is predictable and uniform across the set.
With only 3 tools, the set feels minimal but functional for a memory service. It covers basic operations (store, retrieve, search), but lacks advanced features like updating or deleting memories, which might be expected in a more comprehensive service.
The tools provide core CRUD-like operations for storing and retrieving memories, but there are notable gaps: no update_memory or delete_memory tools, which limits lifecycle management. Agents can work around this for basic use but may encounter dead ends for modifications.