mnemo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNEMO_DB_PATH | No | Database path | ~/.mnemo/memory.db |
| MNEMO_DIMENSIONS | No | Embedding vector dimensions | 768 |
| MNEMO_EMBEDDING_MODEL | No | Embedding model name | nomic-embed-text |
| MNEMO_EMBEDDING_API_KEY | No | API key for cloud embedding providers (required if provider is openai) | |
| MNEMO_EMBEDDING_BASE_URL | No | API base URL for embedding provider | http://localhost:11434 |
| MNEMO_EMBEDDING_PROVIDER | No | Embedding provider: ollama or openai | ollama |
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 |
|---|---|
| rememberB | Store a memory with optional tag, categories, and namespace |
| remember_batchA | Store multiple memories in a single call. Embeds all at once for efficiency. Deduplicates automatically. |
| recallC | Search memories semantically by query |
| forgetA | Delete a memory by ID |
| updateB | Update an existing memory's content or metadata. Re-embeds automatically if content changes. |
| bumpC | Reinforce a memory's weight (recall reinforcement) |
| decayB | Trigger a decay cycle — reduces memory weights based on tag tiers |
| inspectA | View a specific memory or aggregate stats |
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 8 tools
Each tool targets a distinct memory operation: storage (remember, remember_batch), retrieval (recall, inspect), modification (update, bump, decay), and deletion (forget). No overlapping purposes.
Most tools use single verbs (bump, decay, forget, inspect, recall, remember, update) which is consistent, but remember_batch breaks the pattern with a compound name. Minor deviation.
Eight tools cover all core memory lifecycle operations (CRUD plus weight management and batch storage) without being excessive. Well-scoped for a memory management system.
Covers create, read, update, delete, weight manipulation, and batch operations. Minor gap: no explicit listing of all memories without a semantic query, but semantic recall may suffice for typical use.