agent-memory-sqlite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_MEMORY_DB | No | Path to the SQLite database file used for persistent memory storage. | ~/.agent-memory/memory.db |
| AGENT_MEMORY_PROJECT | No | Default project scope for memories. Defaults to the name of the directory the agent runs in. | name of the current directory |
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 | Save a durable fact, decision or convention for future sessions. Saving the same text again refreshes it instead of duplicating. |
| recallC | Search saved memories by keywords. Best matches first (BM25), with recent memories ranked higher. |
| recentB | List the most recently saved or refreshed memories. |
| forgetA | Delete a memory by its id (the #number shown by recall and recent). |
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 4 tools
Each tool maps to a clear memory operation: save, search, list-recent, and delete. The only mild overlap is between recall and recent, since both retrieve memories, but their descriptions distinguish keyword search from recency listing.
Names are short, lowercase, and mostly verb-based (remember, recall, forget). 'recent' is an adjective rather than a verb, which is a minor deviation from the otherwise consistent pattern.
Four tools is well-scoped for a lightweight memory server: save, search, list, and delete cover the core lifecycle without bloat. Each tool earns its place.
The surface covers create, search, list, and delete, with deduplication on re-save. A direct update-by-id operation is missing, but remember's refresh behavior and forget cover most practical workflows.