Memento
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMENTO_HOME | No | Base directory for all storage | ~/.memento |
| MEMENTO_ADMIN_PORT | No | Port for the admin web UI | 3000 |
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 |
|---|---|
| memory_storeA | Create or update a memory. Provide an id to update an existing memory. Memories are persistent across sessions and searchable. Write content that is specific, front-loads key information, and covers one concept per entry. |
| memory_searchA | Search memories using BM25 ranking. Returns snippets (first ~150 chars), not full content. Use memory_recall to fetch full content for specific results. Scope searches with namespace and tags for better relevance. |
| memory_recallA | Fetch full content for specific memory IDs. Use after memory_search to retrieve complete entries for the most relevant results. Only recall what you actually need. |
| memory_deleteA | Soft-delete a memory by ID. The entry is excluded from future searches. Requires the namespace where the memory is stored. |
| memory_list_namespacesA | List all available namespaces with entry counts. Use this to discover what domains of knowledge exist before searching. |
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 purpose: store creates/updates, search finds, recall retrieves full content, delete removes, and list_namespaces discovers domains. No overlapping functionality exists, and the descriptions explicitly differentiate between search and recall.
All tool names follow a consistent memory_verb pattern (store, search, recall, delete, list_namespaces). This makes the set predictable and easy to navigate.
With 5 tools, the server is well-scoped for a memory management system. Each tool addresses a distinct operation without unnecessary redundancy or bloat.
The tool set covers the full lifecycle of memory management: create/update (memory_store), read (memory_recall), search (memory_search), delete (memory_delete), and discovery (memory_list_namespaces). There are no obvious gaps or dead ends.