localmem
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCALMEM_DB | No | Path to the database file, instead of ~/.localmem/memory.db. ~ is expanded. Setting it to an empty or whitespace-only value is an error. | ~/.localmem/memory.db |
| LOCALMEM_NO_TRACKING | No | Any non-empty value makes recall strictly read-only: stops bumping recalled_count and last_recalled_at. The test is emptiness, not truthiness — LOCALMEM_NO_TRACKING=0 disables tracking too. |
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_recallA | Search the user's persistent cross-session memory. Call before answering questions about project history, past decisions, or user preferences. |
| memory_addA | Save a durable fact, decision, or lesson to the user's persistent memory. Call when you learn something worth remembering across sessions. A bug you fought: kind='lesson', one line: symptom — real cause — fix. Always pass keywords: synonyms, Vietnamese+English terms, error codes, symptoms — search is lexical. |
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 2 tools
memory_recall and memory_add serve clearly distinct purposes: one reads memory, the other writes it. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with 'memory' prefix: memory_recall and memory_add. The naming is perfectly predictable.
With only 2 tools, the server is at the bare minimum for a read/write memory store. It feels thin, but the core operations are present.
The server supports add and recall but lacks update/delete operations for memory entries. This is a notable gap for correcting stale facts or removing obsolete memories in a persistent store.