nexus-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search across all memory files by keyword. Returns matching file names, titles, strengths, and context snippets. |
| statsA | Show memory health statistics: file counts per tier, average strength, active/decaying/archived counts. |
| saveB | Save a new memory to a specified tier. Creates a markdown file with frontmatter. Use for recording new information, preferences, or experiences. |
| touchA | Boost a memory's strength (simulate access, counteracts Ebbinghaus decay). Use this when a memory is referenced or found relevant. |
| decayA | Run a dry-run decay check. Calculates Ebbinghaus decay for all memories and reports which would be archived. Does NOT modify any files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Memory Statistics | Nexus memory health overview |
TDQS
Scored across 5 tools
Each tool has a unique and clearly defined purpose: decay for dry-run archiving, save for creating new memories, search for retrieval, stats for health metrics, and touch for strength boosting. No overlap exists.
All tool names are single, imperative verbs (decay, save, search, stats, touch), forming a consistent and predictable pattern. 'Stats' is a noun but functions as a command verb in this context.
With 5 tools, the set covers core memory operations (create, read, update, delete via decay/archiving, and health monitoring) without unnecessary bloat. The count is well-scoped for the server's purpose.
The tool surface covers creation, retrieval, strength management, decay checking, and statistics. A minor gap is the lack of an explicit 'forget' or 'delete' tool, but decay archives memories, and users can boost strength. The set is largely complete for typical memory management workflows.