Holographic Memory MCP
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Store a durable fact, decision or preference; use |
| recallA | Retrieve full memories ranked for a natural-language question. Use this for ordinary recall; use |
| searchA | Find memories with metadata filters or ranking controls; use |
| getA | Read one known memory id in full, including tags, metadata and version. Use an id from |
| forgetA | Delete memories from the active store by id, ids or id prefix; use |
| listA | Browse memories in id order, optionally limited by id prefix or tag; use |
| statsA | Inspect store counts, recall mode, encryption status, storage size and active limits without reading memory contents. Read-only; use |
| exportA | Read a portable snapshot of memory contents as JSON, JSONL or Markdown; use |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| recall-context | Retrieve the memories relevant to a topic and ask the model to use them. |
| save-memory | Ask the model to store a fact or decision with the remember tool. |
| review-memories | Show stored memories and ask the model to propose consolidation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| stats | Counts, recall mode, encryption status and limits. |
TDQS
Scored across 8 tools
Each tool targets a distinct operation, but `recall` and `search` both perform retrieval and rely on the descriptions to separate natural-language lookup from filtered/ranked lookup; `list` also overlaps with `search` for browsing. The descriptions do a good job of redirecting between them, so an agent is unlikely to misselect in practice.
All names are short, single-word imperative/lowercase tokens (remember, recall, search, get, forget, list, export) with `stats` as the only noun form. The convention is consistent and readable, just not a strict verb_noun pattern.
Eight tools is a well-scoped surface for a memory store: write, several read modes, delete, and two introspection utilities. No tool looks redundant enough to remove, and nothing feels missing at the count level.
Covers the full lifecycle: create/overwrite (remember with id/if_version/create_only), read (get, recall, search, list), delete (forget), diagnostics (stats) and snapshot export. The notable gap is an `import`/restore counterpart to `export`, plus explicit tag/metadata-only mutation, which agents must work around by rewriting content.