Memória
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV | No | Path to the uv executable (optional). | |
| HTTPS_PROXY | No | Proxy used by uv and memoria update (optional). | |
| MEMORIA_HOME | No | The folder where memories live instead of the default ~/.memoria. | |
| MEMORIA_LANG | No | Overrides the language used by the app (pt, en, hi, he). Overrides the system language and the saved preference. | |
| PYTHON_VERSION | No | Overrides the Python version used (optional, e.g. 3.12). | |
| UV_SYSTEM_CERTS | No | Set to 1 so uv uses the system certificates (optional, useful with a company proxy). | |
| MEMORIA_SEM_UPDATE | No | Set to 1 to turn off the version check (git ls-remote) and the update network use. | |
| MEMORY_APP_REPO_URL | No | Overrides the repository URL used for updates (default comes from ~/.memoria/config.json or the package's release.conf). | |
| RELEASE_DOWNLOAD_URL | No | Overrides the release download URL template, e.g. {repo}/releases/download/{version}/{file}. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_searchA | Search memories by title, body, project, task, epic and tags. A ticket key (e.g. ABC-123) returns everything for that task and its epic. Filters: project, type, task and epic. |
| memory_addA | Save a memory as Markdown and return the file path. Secrets (tokens, keys, passwords) are redacted before writing. |
| memory_relatedA | Memories related to a memory, strongest relation first: explicit link, same task, same epic, same project, shared files. |
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 3 tools
Each tool has a clearly distinct role: searching memories, finding related memories, and adding a memory. The boundaries are reinforced by descriptions that specify different inputs and outputs.
All tools share the `memory_` prefix and short suffixes, giving a predictable pattern. However, the suffixes mix action-oriented and relational terms (`search`, `add`, `related`), which is a minor inconsistency.
Three tools is a focused, minimal surface for a memory server and avoids bloat. It is slightly underprovisioned for full memory lifecycle management but appropriate for the likely intended lightweight use.
The server covers saving, searching, and relating memories, but lacks update and delete operations, leaving the lifecycle incomplete. Agents may hit dead ends when needing to modify or remove a memory.