Mnemonic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNEMONIC_DATA_DIR | No | Override the default data directory for storing memories. Default is ~/.mnemonic. | ~/.mnemonic |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mnemonic_createA | Create a new memory. Use this to store important information that should persist across sessions. Memories can be tagged for organization and have trigger phrases that surface them when relevant topics come up. Example: - Title: "Bash's communication style" - Content: "Direct, concise, no fluff. Lead with conclusions." - Tags: ["preferences", "user-profile"] - Triggers: ["how does bash like responses"] |
| mnemonic_getA | Get a single memory by its ID. Returns the full memory including content, tags, triggers, and metadata. Also records that the memory was accessed (updates access count and timestamp). |
| mnemonic_updateA | Update an existing memory. Only specified fields will be updated. Tags and triggers are replaced entirely if provided (not merged). Example: - id: "abc-123" - weight: 0.95 # Increase importance - tags: ["high-priority"] # Replace existing tags |
| mnemonic_deleteA | Permanently delete a memory. This cannot be undone. Consider setting status to 'archived' instead if you might need the memory later. |
| mnemonic_searchA | Search memories using full-text search and/or tag filtering. The query searches both title and content using SQLite FTS5. Results are ranked by relevance and weight. Examples: - query: "wishly deals" # Find memories about Wishly deals - tags: ["project"] # All memories tagged 'project' - query: "API", tags: ["technical"] # Combine search and filtering |
| mnemonic_listA | List all memories with optional filtering and sorting. Use this for browsing memories rather than searching. Returns paginated results with metadata. |
| mnemonic_pinA | Pin or unpin a memory. Pinned memories:
|
| mnemonic_exportA | Export all active memories to JSON. Returns a complete export that can be imported later or backed up. Useful for:
|
| mnemonic_importA | Import memories from a previous export. The data must be in the export format with a 'memories' array. Options:
Returns statistics about the import operation. |
| mnemonic_statsA | Get memory statistics. Returns:
Useful for understanding your memory landscape. |
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 10 tools
Each tool targets a distinct operation: create, get, update, delete, search, list, pin, export, import, stats. Search and list are differentiated by intent (query-based vs. browsing), and all other actions are unambiguous.
All tools follow a consistent 'mnemonic_<verb>' pattern (e.g., mnemonic_create, mnemonic_get, mnemonic_update). The verb is clear and the naming is uniform.
10 tools is well-scoped for a memory management server. It covers all core CRUD operations plus search, organization (pin), data portability (export/import), and analytics (stats) without bloat.
The tool set provides complete lifecycle coverage for memories: create, read, update, delete, search, list, plus additional features like pinning, export/import, and statistics. No significant gaps are apparent.