Mnemex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | No | Python path (required for editable installs) | |
| LTM_VAULT_PATH | No | Path to Obsidian vault for long-term memory (optional) | |
| MNEMEX_PL_ALPHA | No | Power-law alpha parameter | 1.1 |
| MNEMEX_DECAY_BETA | No | Sub-linear use count weighting | 0.6 |
| MNEMEX_DECAY_MODEL | No | Decay model (power_law | exponential | two_component) | power_law |
| MNEMEX_DECAY_LAMBDA | No | Decay constant lambda (3-day half-life) | 2.673e-6 |
| MNEMEX_STORAGE_PATH | No | Storage path for JSONL files | ~/.config/mnemex/jsonl |
| MNEMEX_TC_LAMBDA_FAST | No | Two-component fast lambda (~12h) | |
| MNEMEX_TC_LAMBDA_SLOW | No | Two-component slow lambda (~7d) | |
| MNEMEX_TC_WEIGHT_FAST | No | Two-component fast weight | |
| MNEMEX_FORGET_THRESHOLD | No | Threshold for forgetting memories | 0.05 |
| MNEMEX_PL_HALFLIFE_DAYS | No | Power-law half-life in days | 3.0 |
| MNEMEX_PROMOTE_THRESHOLD | No | Threshold for promoting memories to LTM | 0.65 |
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 |
|---|---|
| cluster_memoriesA | |
| consolidate_memoriesB | |
| create_relationA | |
| gcA | |
| open_memoriesB | |
| promote_memoryA | |
| read_graphA | |
| save_memoryA | |
| search_memoryC | |
| search_unifiedB | |
| touch_memoryA | |
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 11 tools
Each tool has a clearly distinct purpose with no significant overlap. For example, cluster_memories groups similar memories, consolidate_memories merges them, create_relation links memories, and touch_memory reinforces a single memory. The descriptions clearly differentiate each tool's function, making misselection unlikely.
The naming follows a consistent verb_noun pattern throughout (e.g., cluster_memories, create_relation, promote_memory), with all tools using snake_case. The only minor deviation is 'gc' (garbage collection), which is an acronym rather than a descriptive verb_noun, but it's a common term in this context and doesn't break overall consistency.
With 11 tools, the count is well-scoped for a memory management system. Each tool serves a specific purpose in the lifecycle of memories (e.g., save, search, reinforce, promote, garbage collect), and none feel redundant or unnecessary for the domain.
The toolset provides comprehensive coverage for memory management, including creation (save_memory), retrieval (open_memories, search_memory, search_unified), reinforcement (touch_memory), organization (cluster_memories, create_relation), promotion (promote_memory), and cleanup (gc). The only minor gap is that consolidate_memories is noted as 'NOT YET IMPLEMENTED', but this is explicitly documented, and other tools cover related functionality.