memshelf-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memshelf_shelveA | Offload one closed topic to the shelf as a durable, indexed episode —
redaction, digest contract and git commit included. Derived files are not
written here — they are rendered by |
| memshelf_lint_digestA | Check a digest against the contract while it is still being written —
the same validator |
| memshelf_recallA | Fetch a shelved episode by id, or one |
| memshelf_indexA | Return the shelf INDEX — the small recall entry point. Read it before answering anything about past work, then recall only what you need. |
| memshelf_searchA | Grep the shelf for episodes matching every query token; returns addresses and snippets. Use when the episode id is unknown. |
| memshelf_statsA | Report the shelf's token economy: standing cost vs shelved mass, claimed compression, realized savings from logged recalls. |
| memshelf_adviseA | Report what your context window is made of and what you could put down — breakdown plus ranked proposals; writes nothing. Pass your window's occupants (label, size, live or not); with none it reports the shelf alone. |
| memshelf_initB | Create (or top up) a memory shelf: layout, categories, INDEX preamble, POLICY.md, shelf.yml. Idempotent; never overwrites existing files. |
| memshelf_rebuildA | Regenerate the derived files (ledger.tsv, .meta.json, INDEX.md,
stats.svg) from the episodes; |
| memshelf_rollupB | Archive a period's episodes behind one digest-of-digests you write,
shrinking INDEX; nothing is deleted. Not the answer to |
| memshelf_purgeA | Drop episodes past |
| memshelf_resolveA | Settle the two-writers-on-parallel-branches conflict: union derived rows, rebuild INDEX, run doctor. Episode conflicts are reported, never auto-merged; safe outside a conflict too. |
| memshelf_doctorA | Diagnose shelf integrity: episode schema, digest contract at rest,
leaked secrets, ledger consistency, INDEX budget. Read-only; fixes
nothing. |
| memshelf_importA | Retro-shelve an exported dialog without pulling it through context:
|
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 14 tools
Each tool targets a clearly distinct operation within the memory-shelf lifecycle: reading (index, recall, search), writing (shelve, import), diagnostics (lint_digest, doctor), maintenance (rebuild, rollup, purge, resolve), and insights (stats, advise). Potential overlaps like lint_digest vs. doctor or rebuild vs. resolve are explicitly differentiated by scope and timing in the descriptions.
All 14 tools consistently use the memshelf_ prefix and lower snake_case. The action/artifact naming is predictable across the set, even when a few names are noun-like (stats, doctor) rather than purely verb_noun.
With 14 tools, the server sits in the well-scoped 3-15 range and covers a full lifecycle without obvious filler. Each tool maps to a distinct phase or concern of managing a memory shelf.
The surface covers initialization, creation, import, retrieval, search, metrics, validation, rebuild, rollup, retention purge, conflict resolution, and diagnosis. Minor gaps remain, such as no direct per-episode edit, manual delete, or export operation, though retention and rollup mitigate deletion and archival needs.