memento-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMENTO_PROFILE | No | Language profile for stop words and trivial prompt classifiers. Options: english, portuguese, spanish. | english |
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 |
|---|---|
| memory_storeA | Persist a fact, decision, lesson, or pattern so it can be recalled later by |
| memory_searchA | Ranked full-text + decay-weighted search across SQLite, file-memory sources, and (when configured) the Obsidian vault. Read-only. Use the three-layer progressive-disclosure pattern: |
| memory_getA | Fetch the full body, tags, and metadata of one memory by id (~300-800 tokens). Read-only. Use after |
| memory_timelineA | Return the chronological neighbourhood of memories around an anchor id (~200 tok/neighbour). Read-only. Use after |
| memory_dedup_checkA | Cheap pre-flight (~50 tok/match): "would storing this content duplicate something I already have?" Read-only. Use before |
| memory_listA | Browse stored memories with optional filters — ordered by recency/importance. Read-only. Use to enumerate by type/scope/project. Prefer |
| memory_deleteA | Soft-delete a memory by id — the row is hidden from search/list/get but retained for audit. Idempotent. Use for accidental or obsolete memories. To replace one with a corrected version, prefer |
| decisions_logA | Multi-action ADR log. Pick one via |
| pitfalls_logA | Multi-action log of recurring problems and their resolutions. Pick one via |
| memory_analyticsA | Reports utility rates of injected memories, token costs per search layer, auto-capture stats, compression activity, and prune suggestions. Read-only. Use to tune importance thresholds, find dead memories worth pruning, and verify that auto-capture/compression are earning their keep. Returns a no-op message when analytics are disabled. |
| memory_updateA | Edit a memory in place — only the fields you pass are changed. Editable: |
| memory_pinA | Toggle the pinned flag — pinned memories survive pruning and rank higher in search. Idempotent. Use sparingly: reserve pins for canonical decisions, user preferences, and high-leverage facts. Pinning everything defeats the purpose. |
| memory_compressA | Force one compression cycle now: cluster similar memories by embedding similarity, merge each cluster into a canonical memory, and mark originals as compressed. Use after a bulk import or to sanity-check compression. Compression normally runs on the maintenance schedule. Side effects: writes merged memories, updates originals' |
| memory_exportA | Export memories, decisions, and pitfalls as a portable JSON document. Read-only. Use before destructive maintenance (bulk delete, schema migration) so you have a clean restore point, or to transfer state to another memento-mcp instance via |
| memory_importA | Import memories, decisions, and pitfalls from a JSON file produced by |
| memory_linkA | Create a typed directed edge between two memories. Edge types: |
| memory_unlinkA | Remove a previously created edge — pass the exact |
| memory_graphA | BFS walk from one memory id outward, returning neighbour nodes + typed edges. Read-only. Use after |
| memory_pathA | BFS shortest path between two memories — returns the chain of ids + edge types, or a |
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 19 tools
Each tool has a clearly distinct purpose: decisions_log for ADR entry, pitfalls_log for problem tracking, and memory_* tools covering CRUD, search, graph, linking, analytics, etc. No two tools overlap in functionality.
Most tools use the 'memory_' prefix with a verb or noun (e.g., memory_store, memory_search), but decisions_log and pitfalls_log break the prefix pattern. The naming is mostly consistent and intuitive.
19 tools is well-scoped for a knowledge management server. The count covers all necessary operations without being excessive, and each tool contributes a unique, valuable function.
The tool surface is comprehensive: store, retrieve, update, delete, search, list, graph traversal, import/export, dedup, compression, pinning, linking/unlinking, timelines, decisions, pitfalls, and analytics. No obvious gaps.