Mneme Memory MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNEME_HOME | No | Primary Mneme home override. If set, overrides HERMES_HOME and default. | |
| HERMES_HOME | No | Hermes-compatible memory home. Used if MNEME_HOME is not set. | ~/.hermes |
| MNEME_DB_PATH | No | SQLite fact store path. | $HOME/memory_store.db under resolved home |
| MNEME_MEMORY_DIR | No | Markdown memory directory. | $HOME/memories under resolved home |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_summaryA | Return the always-on shared memory summary. |
| memory_searchC | Search the shared memory fact store. |
| memory_listB | List recent facts from the shared memory fact store. |
| memory_addA | Add a durable fact to shared memory. Use target='user' for identity, preferences, and working style. Use target='memory' for projects, tools, paths, decisions, and setup notes. |
| memory_updateC | Update a fact by id. |
| memory_removeA | Remove a fact by id and remove the matching Markdown bullet if present. |
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 6 tools
Each tool has a clearly distinct purpose: add, list, remove, search, summary, update. There is no conceptual overlap; an agent can easily select the correct tool.
All tools follow a consistent 'memory_verb' pattern using snake_case. The naming is predictable and aids discoverability.
Six tools is an ideal count for a focused memory server. Each tool addresses a specific need without bloat, covering core CRUD and search operations.
The tool surface covers add, read (list, search, summary), update, and delete. Missing a bulk operation (e.g., clear memory) is a minor gap but not critical for typical usage.