MemVault
MemVault is a shared, MCP-native memory layer for AI agents, exposing tools to store, retrieve, review, inject, and govern persistent memories across sessions and agents.
Save, extract, search, review/edit, confirm-read, list, and delete/forget memories.
Start sessions with auto-injected MUST/REFERENCE context and track compliance/effectiveness.
Record or infer task outcomes, with failures distilled into future lessons.
Manage evidence and provenance via supports/contradicts/sourced_from relations and evidence-chain lookup.
Import skills from Markdown SOPs and run dedup, decay, and promotion maintenance.
Filter by namespace, type, priority, agent, and use optional agent API-key auth.
Plugs into a local Ollama instance as the embedding and chat-LLM provider — nomic-embed-text for semantic search vectors and models like qwen2.5 for structured memory extraction, failure reflection, and relation extraction — keeping all memory processing on the user's machine.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MemVault remember that I prefer pnpm over npm for all projects"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MemVault
The Shared Memory Layer for Every AI Agent You Run
Not "agent learns to search memory" — memory finds the agent.
MCP Native · Hybrid Retrieval · Auto-Injection · Zero-Config Sync
Open Source · Self-Hosted · Private · MIT Licensed
English · 简体中文
If MemVault solves a real problem for you, a star helps others find it.
curl -fsSL https://raw.githubusercontent.com/dreamor/memvault/master/scripts/install.sh | bashEvery AI agent session starts from scratch. Claude Desktop doesn't know what Cursor just learned. DeepSeek Harness (dsh) doesn't know what you told Claude Code yesterday. Whatever agent you're running — international or domestic, IDE plugin or CLI harness — it forgets your preferences every time you start a new conversation.
You've been manually repeating context — project conventions, personal preferences, past decisions — across agents that should already know. This isn't a limitation of the models. It's a missing infrastructure layer.
MemVault is that layer. A lightweight, self-hosted memory router that sits between your agents and their context. It speaks plain MCP — no MemVault-specific SDK, no per-agent API integration. Any MCP-compatible agent, from any vendor, automatically shares the same persistent memory the moment it connects.
Who it's for:
Anyone running an MCP-capable agent — Claude Code, Claude Desktop, Cursor, Cline, Continue, DeepSeek Harness (dsh), or any other MCP client, domestic or international — who wants preferences, project context, and past decisions to persist across sessions without repeating yourself
Multi-agent power users running several of the above side by side, on different models, from different vendors — all sharing the same memory without configuration
Platform teams deploying AI-assisted workflows where consistency matters across a mixed agent fleet: code review conventions, architecture decisions, project-specific preferences
Anyone tired of telling their AI the same thing twice — MemVault works the way your brain should: you say it once, it's there when you need it, no matter which agent is asking
Quick Start · How It Works · What MemVault Gives You · Why MemVault · MCP Server · CLI Reference · Integrations · Architecture · Project Status · Testing · Documentation · Contributing · License
Quick Start
Don't install MemVault by hand — paste this one prompt into Claude Code, Codex, Cursor, dsh, or any other MCP-capable agent. It points the agent at a machine-readable install guide, so the agent does the whole setup itself:
Install MemVault as your long-term memory and wire it into this agent. Fetch and follow https://raw.githubusercontent.com/dreamor/memvault/master/docs/AGENT-INSTALL.md — install the binaries, register MemVault as an MCP server for this host, and verify recall works. Then keep saving my preferences, project decisions, and lessons from each session so my next agent starts with them instead of from scratch.Or install manually:
# Install (Linux / macOS): official script, auto-verifies SHA-256
curl -fsSL https://raw.githubusercontent.com/dreamor/memvault/master/scripts/install.sh | bash
export PATH="$HOME/.memvault/bin:$PATH"
# Windows (PowerShell):
# powershell -ExecutionPolicy Bypass -File scripts\install.ps1
# Homebrew (Apple Silicon):
# brew install dreamor/tap/memvault
# Or from crates.io:
# cargo install memvault-cli memvault-mcp
# The installers auto-start the local REST backend (host of the Web
# Dashboard). Open it, or start it on demand:
memvault-cli dashboard
# Save a MUST-level preference (injected as instruction, agent must follow)
memvault-cli save --content "User prefers Python" --priority MUST --type preference \
--instruction "Use Python for code, not Java" --tags "coding,python"
# Search across all memory (hybrid: keyword + semantic when embedding is enabled)
memvault-cli search --query "Python"
# See what context gets injected when a specific agent connects
memvault-cli session-start --agent-id claude-desktop --context "Help me write code"
# Extract structured memories from free text
memvault-cli extract --text "I prefer dark mode. Our project uses Rust." --save
# Auto-generate agent instruction files from memory
memvault-cli sync
# All in one: dedup, decay, archive stale memories
memvault-cli dedup && memvault-cli decaySystem requirements:
Prebuilt Linux binaries (install script / GitHub release): glibc ≥ 2.39 + GLIBCXX_3.4.31 (GCC 13-era runtime — Ubuntu 24.04+ / Fedora 40+ / Arch). Release builds are pinned to Ubuntu 24.04 runners, and the release workflow gates the highest glibc/GLIBCXX symbol version every binary may require plus a startup smoke test, so this floor cannot silently drift upward (0.6.9 shipped x86_64 binaries requiring glibc 2.43 that way). TLS is rustls, so no OpenSSL dependency. Ubuntu 22.04 / RHEL or EL8/EL9 users: use the Docker image (
dreamor/memvault) or build from source.Building from source (
cargo install/cargo build): links fastembed's prebuilt ONNX Runtime static library and needs a GCC 13-class toolchain. Older toolchains (e.g. GCC 8, CentOS 7/8-era libstdc++) fail at link time with missing C++20/23 stdlib symbols (std::format,std::to_chars). macOS / Windows (MSVC) / Homebrew / Docker are unaffected.
Verify your install in 5 seconds:
memvault-cli --version
# memvault 0.7.2
# sanity check: list saved memories (verifies DB is healthy)
memvault-cli listLocal Ollama Demo (Zero Cost, Stays on Your Machine)
MemVault is plug-and-play with a local Ollama: unconfigured LLM extraction (full-text understanding / failure reflection / relation extraction) auto-detects a local Ollama; embeddings use the local model with the ollama or auto provider.
# 1. Install and start Ollama
brew install ollama && brew services start ollama # or the official installer
# 2. Pull models
ollama pull nomic-embed-text # embeddings, 768-dim (default for ollama/auto)
ollama pull qwen2.5:3b-instruct # chat: LLM extraction/reflection (default qwen2.5:7b, use 3b on small machines)
# 3. (Optional) Pin the providers explicitly — persist them in ~/.memvault/.env
# (shell exports also work — env vars take precedence over the file — but the file survives reboots)
mkdir -p ~/.memvault
cat >> ~/.memvault/.env <<'EOF'
MEMVAULT_EMBEDDING_PROVIDER=ollama
MEMVAULT_LLM_EXTRACTION_PROVIDER=ollama
MEMVAULT_LLM_EXTRACTION_MODEL=qwen2.5:3b-instruct
EOF
# 4. Verify
memvault-cli status # Embedding provider: configured and reachable
memvault-cli save --content "Build server IP is 10.20.30.40" # output (embedded int8)
memvault-cli outcome --task "Deploy trading service" --status failure --cause "Disk space insufficient" --task-type deploy
# → Lesson (Llm): ... means failure reflection ran through the local LLM (not the rule-based fallback)With no configuration at all (neither env vars nor ~/.memvault/.env), LLM extraction auto-detects a local Ollama and enables itself (default model qwen2.5:7b; pull it in advance with ollama pull qwen2.5:7b, or point MEMVAULT_LLM_EXTRACTION_MODEL at an installed model). Embeddings still default to the in-process native embedder; set MEMVAULT_EMBEDDING_PROVIDER=auto in ~/.memvault/.env to prefer Ollama and fall back to native when it isn't running. The native model's first launch downloads the weights from HuggingFace silently in the background — the server/dashboard come up immediately and hot-swap to semantic search once the download finishes, so a fresh install never blocks on it (set MEMVAULT_EMBEDDING_PROVIDER=none to run pure keyword and skip the download).
Related MCP server: GNB MemoryMCP
How It Works
MemVault is a pipeline, not a single script. Every stage below is a shipping module:
Agent connects (MCP stdio/SSE)
│
▼
┌───────────────────┐
│ Agent Router │ ← match agent type/tag → filter relevant memory
│ (Agent Registry) │
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Memory Retrieval │ ← keyword (BM25) + vector (embedding) + RRF fusion
│ (3 search modes) │ synonym expansion · scoring · soft filtering
└────────┬──────────┘
│
▼
┌───────────────────┐
│ Auto-Injection │ ← MUST-level → instruction prompt
│ │ REFERENCE → context resource
│ │ NORMAL → search result
└────────┬──────────┘
│
▼
Agent receives context ──→ makes better decisionsStorage: SQLite with bundled FTS5 (full-text search); embeddings stored int8-quantized (~1/4 the size of f32 at near-identical ranking quality, legacy f32 rows still readable)
Retrieval: BM25 keyword search over FTS5 with CJK bigram tokenization (Chinese two-character words match correctly) and tiered match fallback (strict → relaxed unigram → synonym OR; relaxations are reported, never silent), local-first embedding (in-process native by default — switch to local Ollama or any OpenAI-compatible model), RRF fusion with per-result recall provenance (
kw#2/vec#5), synonym expansion, relevance scoring, soft intent filteringPipeline: Automatic entity extraction, delta-write on save (near-duplicates skipped, similar memories absorb only the residual), semantic deduplication, time-based decay, archive of stale memories
Sync: Zero-invasion file generation —
memvault-cli syncproduces CLAUDE.md, AGENTS.md, etc. directly from database contents
What MemVault Gives You
Auto-Injected Context: Session start automatically pulls relevant memory by agent identity — MUST-level rules land as instructions, not just chat history
Hybrid Retrieval: BM25 + vector + RRF fusion with synonym expansion, relevance scoring, and per-result provenance (which path recalled each memory, at what rank) — available via CLI, MCP tool, and REST API
Explainable Injection: every candidate dropped on the way into an agent's context is recorded with a reason (budget, caps, intent/type penalties) — "why didn't the agent get this memory?" always has an answer
Degrade Before Dropping: when the token budget runs out, a memory is shortened — excerpt, then summary — rather than cut, so more of the ranked list stays reachable at a lower per-memory cost. Shortened text always carries a
[…]marker and the level is reported separately from the dropped list, because an abbreviation that looks complete is worse than a drop. MUST is never shortened: a binding rule with its qualifying clause summarised away is worse than one that overflowedMUST Enforcement: MUST-priority memories are never filtered or truncated. Always in context, always obeyed — trust comes from provenance (human-authored/reviewed), with an opt-in fallback for memories independently corroborated by multiple identity-verified agents (
MEMVAULT_CORROBORATION_GATE), so a single spoofed/compromised agent can't unilaterally inject a binding MUSTMulti-Agent Awareness: Agent Registry with type/tag-based soft filtering (score demotion, not hard exclusion)
agent_idIs Provenance, Not a Filter: retrieval never filters byagent_id— the field only records which agent wrote a memory (source_agent). Every agent searches the same shared corpus; per-agent differences apply only at injection time (type/tag soft scoring viaagents.yamlinject_rules)MCP Proxy: Transparent proxy that injects memory into ANY upstream MCP server's responses — zero client changes
Compliance Tracking:
inject_session_idtraces what was injected and measures follow-through rateCross-Platform: CLI + MCP Server (stdio & SSE) + Web Dashboard (browser) + Obsidian Plugin
Zero-Invasion Sync: Generate AGENTS.md / CLAUDE.md from memory — no per-agent config files to edit. Applies the same exclusions as session injection (unreviewed drafts behind the review gate, superseded facts, pending edit proposals, expired memories) and reports how many it held back and why, so "why isn't this rule in my AGENTS.md" has an answer
Contextual Extraction, Local-First: Rule-based keyword extraction by default; optionally understands a full user+assistant exchange via an LLM, auto-detecting a local Ollama for free before ever touching a remote API
History & Rollback: Every update/delete is snapshotted into
memory_history—memvault-cli checkpoints+memvault-cli restoreroll one memory back without touching the restTime Travel (
as_of): ask what MemVault believed at any past instant —memvault-cli as-of <id> --at 2026-08-01T00:00:00Z,list --as-of,search --as-of,search_memory,POST /api/search. Reconstructed from the same snapshot chain that powers rollback, so it needed no new version schema. Memories deleted or superseded after that instant still come back, because they were the current truth then. Search also recalls from a historical full-text index, so a memory reworded sinceas_ofis still found by the words it had — those hits are taggedhist-kw#Nto keep "matched today" distinct from "matched then". Each answer says where it came from (live row vs. a named history snapshot), so a far-back result is never mistaken for a current oneTwo Time Axes, Never Folded:
as_ofasks what did MemVault believe in March;--occurred-from/--occurred-toask what happened in March. A memory can be true for both answers at once, so they are separate parameters rather than onesince/untilrange — folding them is what makes one of the two questions permanently unanswerable. Undated memories never match an event-time window, and the CLI says so whenever the flag is used rather than only when the result comes back emptySelf-Expiring Facts (
expires_at): a temporary fact ("the deploy freeze runs until Friday") retires itself instead of decaying slowly and being re-injected as stale truth.save --expires-at <RFC3339>or--ttl 7d. Past the bound it leaves retrieval and injection but stays inspectable and restorable — expiry retires a fact, onlyforgeterases one. Honored even for MUST: an explicit bound is not the inferred disuse signal thatmust_exemptprotects againstSelf-Diagnostics:
memvault-cli statusreports exactly which features are degraded when no embedding provider is configured, plus a schema fingerprint (migration version + checksum) for cross-database comparisonEpisodic Memory:
record_outcomerecords task results; failures are distilled into lessons and auto-injected next time (REFERENCE → MUST only with human approval), so the same trap isn't hit twiceProcedural Skill Activation: skills whose
triggermatches intent are injected as structured[SKILL]blocks with success-rate stats (shown after ≥3 runs); failures flag the skill for revision (version++on human edit), repeated successes auto-draft new skills into the review inboxSemantic Knowledge Links: lightweight relation triples, repeated facts consolidated into a linked semantic fact with provenance, and superseded facts archived (never re-injected, still listable & restorable)
Team Shared Pool & SOP Import: memories marked
sharedare injected into every session (capped at 20); Markdown SOPs can be batch-imported as verifiable skillsDelta-Write on Save: every save is checked against its namespace first — near-duplicates are skipped, similar memories absorb only the residual (what's genuinely new) and get their strength refreshed, so the library converges instead of accumulating near-copies;
--force/force_insertbypassesTask-Level Evaluation:
memvault-cli benchsamples your own failure history (episodes that distilled a lesson) and measures lesson retrieval/injection rates — and with--judge, an LLM scores "plan without vs. with memory" against the known failure cause, so you see task-success lift, not just retrieval recallTwo-Phase Injection (never blocks): MUST rules resolve deterministically with zero embedding calls and are served immediately; the semantic pipeline prefetches in the background and lands within a short window (250ms) — if it doesn't, the deterministic baseline is served and the request moves on (two-phase design)
Conversation-N-Gram Retrieval: retrieval keys are conditioned on the recent turn window, weighted by recency so the current focus dominates — not a single flat query
Single Canonical Injection Channel: per-agent
inject_channel(mcp/proxy/syncinagents.yaml) restricts automatic injection to one delivery path, so the same memory is never sent to the same agent twiceData You Own: Single SQLite file. Full export/import. No cloud dependency. Your data, your machine.
The Index Is Disposable, the Memory Is Not: every derived structure in MemVault can be thrown away and rebuilt, so a corrupt or stale index is never a data-loss event.
markdown backend — the
.mdfiles are the memory;.memvault-cache.dbis a shadow index derived from them. Delete the cache and the next open rebuilds it from the vault. Edit a file by hand in Obsidian, in an editor, or viagit checkout, andmemvault-cli reindex(or--watch) reconciles it — content is diffed against the cached row and resynced on any mismatch. Your memories are plain text you cangrep,git blame, and take to any other tool.sqlite backend —
data.dbis the source of truth, and the derived parts inside it still self-heal: the FTS index is rebuilt automatically on open whenever its row count disagrees withmemories, and the embedding column can be dropped and backfilled (switch embedding models, or run with no provider configured and add vectors later).What is never derived: your content, your review state, your provenance, and the
memory_historysnapshot chain that powers rollback andas_oftime travel. Note the one asymmetry — history snapshots live in the cache, so on the markdown backend a rebuilt cache loses the version chain and point-in-time reads fall back to the live row (docs/DESIGN.md§9.6). Expiry and everything else survive a rebuild intact.
Why MemVault
Storing and retrieving memories is solved — a dozen products do it well, and since 2025 the Code Agents do it natively. What is not solved is the part after retrieval: getting one shared corpus into every agent you run, deciding what entitles a memory to bind that agent, and knowing whether it obeyed.
The claims below come from a 15-product survey refreshed 2026-11
(docs/DESIGN.md §2). They
are falsifiable — the table there names every product and every source.
What only MemVault does
Capability | What it actually means | Who else has it |
Follow-through tracking |
| Nobody. The closest is agent-memory's |
Instruction-layer enforcement | MUST memories are never filtered, never truncated, and are rendered as directives rather than context. A memory becomes a constraint, not a suggestion | Nobody. |
Trust-gated binding | What entitles a memory to bind an agent: provenance, identity verification, and an opt-in corroboration gate so one spoofed or compromised agent cannot unilaterally inject a MUST everyone obeys | Nobody. Multi-tenant ACLs answer who may access; this answers what may be believed. Different axis, and the survey has no column for it |
Injection explainability | Every candidate dropped on the way into an agent's context is recorded with a reason — budget, cap, intent penalty, review gate. "Why didn't the agent get this memory?" always has an answer | agent-memory has retrieval trajectory (what was recalled). Nobody reports what was dropped and why |
Review-gated agent edits | An agent can propose a correction to any memory, including a MUST — as a pending proposal that leaves the target live until a human decides | Nobody. Letta's agent self-edits memory directly, which is its own listed weakness |
Task-level evaluation |
| Nobody. Every published number in this space is a recall metric |
What MemVault does differently
Claude Code Auto Memory | Codex Memories | Mem0 | Zilliz memSearch | MemVault | |
Which agents see the memory | Claude Code only | Codex only | whatever embeds its SDK | per-tool plugins | every agent you run, from one store |
How it reaches the agent | platform loads its own files | platform loads its own files | you call | you call | auto-injected over MCP, proxy, or generated |
Works without MCP | ✅ (its own files) | ✅ (its own files) | ❌ | ❌ | ✅ — |
Source of truth | agent-written notes | session summaries | vector store | Markdown files | your choice: SQLite, or Markdown files with a rebuildable shadow index |
Runtime | bundled | bundled | Python + a vector DB | Python + Milvus | one Rust binary, no service, no Python |
Injection latency | — | — | p50 ≤ 1.1 s (published) | — | p50 ≈ 1.2 ms for the deterministic MUST path, measured with no embedding provider at all (§2.6) |
On that latency comparison, honestly. The two numbers are not measured the same way and should not be read as a like-for-like win. Mem0's published p50 covers its whole retrieval pipeline; ours is the
/api/sessioninjection call alone, from a 20-probe plumbing run against a local debug build with no embedding provider configured. The defensible claim is narrower and still worth making: MUST resolution does not touch an embedding model at all, so its latency does not depend on one being installed, warm, or reachable — that is §6.1.2's two-phase design, and it is whyedge-litecan turn embeddings off without losing MUST injection. A comparable end-to-end number needs the BEAM scored run, which has not happened.
Platform-native memory is the real competition now, and it is good — zero infrastructure, zero configuration. Its structural ceiling is that each platform only loads its own silo: Claude Code's memory directory is invisible to Cursor, and Codex's memories do not leave Codex. If you run more than one agent, that is the gap.
Where MemVault is behind
Stated plainly, because a comparison that only lists wins is not a comparison:
Leader | MemVault today | |
Multimodal input | agent-memory (image/audio/video, text projections) | text only |
Graph relations | Zep/Graphiti (temporal KG, multi-hop) | single-table one-hop triples; a real graph is deferred until relation volume demands it |
Cloud / team-hosted tier | memSearch (Lite → Docker → Cloud), Mem0 | local-first only, by choice — see the positioning constraint in §15 |
Time travel over the vector path | Zep (bi-temporal graph) |
|
Published benchmark scores | Mem0, memU, Zep (LoCoMo / DMR / LongMemEval) | harness built and plumbing-validated on BEAM, no scored run yet — deliberately not chasing LoCoMo, which a 1M-token context window now scores competitively without any memory system |
Everything in that table is tracked in §15 with either a plan or a reason it is not being done.
MemVault complements your existing agent setup rather than replacing it. Keep your LLM, your IDE, and your workflow exactly as they are. MemVault adds the memory layer underneath — and the part that checks whether it was used.
MCP Server
Tier-1 agents (Claude Code, OpenCode, dsh, Gemini CLI, Codex) have one-command plugin installs — see Installing into your agents first. Everything below is the universal fallback for any other MCP client.
stdio (any standard MCP client)
MemVault speaks plain MCP stdio — the same mcpServers JSON works verbatim in Claude Desktop, Cursor, Cline, Continue, and any other client that reads this format:
{
"mcpServers": {
"memvault": {
"command": "/path/to/memvault-mcp",
"args": ["--db", "~/.memvault/data.db"],
"env": { "OPENAI_API_KEY": "sk-..." }
}
}
}A couple of clients use their own one-liner instead of hand-editing JSON:
# Claude Code
claude mcp add memvault /path/to/memvault-mcp -- --db ~/.memvault/data.dbDeepSeek Harness (dsh) — a domestic (China) agent harness — gets deeper treatment than a generic stdio config: a native Cordis plugin (dsh-plugin/) that auto-injects memory into the system prompt and auto-extracts at turn end, with no per-turn cooperation required from the agent. See docs/INSTALL.md §2.5 for both the zero-code MCP route and the deep-integration plugin.
Other MCP-compatible agents — international or domestic, IDE plugin or CLI harness — should work the same way: any client implementing standard MCP stdio/SSE can connect without MemVault-side changes. The ones above are the ones we've actually verified; if you get MemVault working with another one, a PR to this list is welcome.
SSE (multi-client, network-accessible)
memvault-mcp --transport sse --port 3777
# Clients connect at http://127.0.0.1:3777/mcpSSE features: multi-client simultaneous connections, auto-triggered embedding backfill on initialization, HTTP remote access.
Note:
--transport sseonly mounts the MCP-over-HTTP endpoint (/mcp) — it does not expose the REST API (/api/*). The Web Dashboard is served by the REST backend (memvault-mcp --transport http --serve-web <dist>), and the Obsidian plugin also uses the REST API and requires--transport httpinstead. See docs/INSTALL.md §2.6.
21 MCP Tools
Tool | Description |
| Save with auto-embedding; delta-write by default (near-dupes skip, similar merge) — |
| Record a task outcome (episodic memory); failures reflect into lessons |
| Classify + record a task outcome from host-provided evidence (friction counts, terminal state) instead of a raw transcript — same rule-floor-plus-optional-LLM-judge logic as the Stop hook's |
| Import skills from a Markdown SOP (headings → skills, list items → steps) |
| Hybrid (default) / keyword / semantic; semantic modes fall back to keyword when embeddings are unavailable |
| Agent-aware context injection; honors the agent's |
| Propose a text edit to a memory for human review — creates a pending memory carrying the edit and leaves the target untouched and still injecting. Approving supersedes the target; rejecting discards the proposal. |
| Approve / reject / edit; edit also works on already-approved memories, reject only applies to pending ones. Approving a pending proposal also supersedes its target |
| Soft delete — removes the live row and cascaded evidence relations, restorable via CLI |
| Permanently erase one memory or a criteria-matched bulk set (GDPR-style, irreversible); |
| Structured extraction from text |
| Read-only deduplication scan (reports near-duplicates; does not merge/delete) |
| Decay + auto-archive; opt-in permanent auto-forget when |
| Mark read (increments |
| List memories pending human review; |
| Promote pipeline (L1→L2→L3), archive sources to L0 |
| Report follow/violate status for an injected session; bad items are skipped, so check the returned updated/total counts |
| Compliance rates per session or aggregate |
| Record evidence relations: supports / contradicts / sourced_from; identical relations are rejected rather than duplicated |
| Get the raw-evidence chain a memory was distilled from (its L0 trace rows) plus its evidence profile — read-only grounding, so an agent can quote the original session text and name its sources |
| Automatic effectiveness judgments for injected memories (useful/neutral/harmful/insufficient-context rates, judged from |
2 MCP Resources
URI | Content |
| MUST-level rules, auto-loaded on connect. Review-gated: only human-reviewed rules are served, the same gate |
| REFERENCE-level project context. Deliberately not review-gated — it may include unapproved AI-extracted drafts, labeled as such in the body. See |
Configuration (.env file & environment variables)
Copy .env.example to ~/.memvault/.env and uncomment what you need — it is also the single source of truth documenting every key.
Precedence (high → low): CLI flags > process environment > ~/.memvault/.env > MEMVAULT_PROFILE scenario profile > built-in defaults. Every binary loads the env file first thing at startup; --env-file <path> or MEMVAULT_ENV_FILE points elsewhere, and a missing file is silently skipped. memvault-cli status prints where each setting came from (env / file / profile / default).
Don't want to read fourteen switches? memvault-cli init --profile <name> writes a coherent bundle instead — coding-agent, assistant, team, edge-lite — with each line commented by its rationale (init --list shows them all, --dry-run previews). A profile is the lowest-precedence layer: it fills only keys your shell and env file leave unset, so leaving one configured permanently can never silently undo your own tuning. It writes no secrets, only provider names. See .env.example for what each profile sets and why.
Two groups are intentionally not in the table below: the host installation contract (MEMVAULT_AGENT_ID, MEMVAULT_HOOK_EXTRACT, … — per-agent values authored in each host's plugin/mcpServers config), and the proxy's upstreams topology (structured data, lives in ~/.memvault/proxy.yaml).
Variable | Purpose | Default |
| Scenario profile applied at startup: | (none) |
| Provider: |
|
| API key for remote providers (not needed for local Ollama); the default | (not needed — |
| Any OpenAI-compatible base URL (OpenAI / Azure / vLLM / gateway...). For |
|
| Embedding model: |
|
| Vector dimensions |
|
| Explicit native model cache directory, independent of the vault; supports |
|
| Optional: enables LLM-based contextual memory extraction (understands a full user+assistant exchange, not just keyword lines). Unset/ | (unset — local-first, rule-based if no local Ollama) |
| Chat-completions endpoint config for LLM extraction | local: |
| Opt-in LLM relation extraction: | (unset / false) |
| Delta-write on save: dedup within the same namespace first — near-duplicates skipped, similar memories absorb the residual. | true |
| How many recent observed turns build the recency-weighted retrieval key used by proxy auto-injection |
|
| Minimum friction score (tool retries, rejected tool calls, mid-session corrections) a Stop-hook-triggered |
|
| Minimum friction score for a Stop-hook |
|
| Minimum LLM-judge confidence to accept its |
|
|
|
|
| Per-job deadline for the REST server's compliance worker; on expiry the remaining rows become |
|
| Idle poll interval for the compliance worker |
|
| Set to | (off) |
| Record whether a | true |
| Opt-in MUST trust path: a MUST memory independently corroborated by enough distinct identity-verified agents (see | false |
| Minimum distinct identity-verified agents required for the corroboration gate above |
|
| Injection gate, on by default: any AI-extracted memory a human has not reviewed is removed from injection entirely — every priority, not just MUST — across the CLI/MCP body, the MCP | true |
| Legacy MUST-only render gate, kept for compatibility and as defense-in-depth when the broad gate above is disabled: with | false |
| SQLite connection pool size |
|
| Comma-separated allowed CORS origins for REST (unset = localhost only) | (localhost only) |
| Seconds |
|
| Web Dashboard static-asset directory served on | embedded |
| Path-list ( | — |
| Background auto-forget: permanently purge memories archived longer than the retention window (irreversible, unlike decay's reversible archiving) |
|
| Archived-retention window (days) for the auto-forget sweep |
|
| Protect MUST memories from forget unless the caller explicitly overrides ( |
|
| Exclude shared-visibility memories from the auto sweep (manual/bulk forget can still purge them) |
|
| SQLite database path |
|
| Storage backend: |
|
| markdown-backend data directory (also | — (markdown mode only) |
| Who is trusted to set a Markdown file's own trust metadata. |
|
| Log verbosity |
|
| Base directory: where |
|
| Path to the env file ( |
|
| HuggingFace endpoint override for native model downloads (e.g. | (HuggingFace default) |
| Proxy-path contextual extraction of agent-produced text: on by default but saved downgraded ( | (on — downgraded) |
CLI Reference
save · outcome · search · list · as-of · init · review · delete · session-start · compliance-enqueue · compliance-finalize · resource · extract · dedup · decay · forget · forget-log · doctor · promote · backup · export · export-skill · import · import-skills · import-agent · ingest · confirm-read · backfill-embeddings · sync · reindex · migrate-to-markdown · checkpoints · restore · supersede · propose-edit · update · status · bench · eval-history · server start|status|stop · dashboard
memvault-cli <command> --help # detailed usage per commandKey Commands
Command | What It Does |
| Apply a scenario profile — |
| Save a memory with priority, type, optional instruction. Delta-write by default: near-duplicates are skipped, similar memories absorb the residual; |
| Record a task result (success/failure/partial); failures are distilled into lessons that auto-inject into similar future tasks |
| Hybrid retrieval with relevance scoring; flags: |
| Show one memory as it stood at a past instant: |
| Propose a text edit to a memory, for human review: |
| Update an existing memory in place: only the flags you pass change — |
| List memories; |
| Simulate what context an agent receives on connect; a multi-line |
| Parse free text, extract structured memories |
| Import skills from a Markdown SOP ( |
| Cold-start import from another agent's native memory files: Claude Code/Desktop ( |
| Incrementally ingest agent session transcripts (Claude Code / Codex / Hermes) into memory: turns with extractable signal are kept as L0 evidence rows, and their extracted candidates carry |
| Generate agent instruction files (AGENTS.md / CLAUDE.md / MEMORY-INDEX.md, …) from memory (with |
| Scan and merge semantically duplicate memories (vector-assisted when an embedding provider is configured) |
| List memory history snapshots (per-memory or global); flags: |
| Revert a memory to the state captured by a checkpoint ( |
| Archive an old fact and point it at its replacement (nothing is deleted; search skips superseded, list keeps them) |
| Show embedding provider readiness (distinguishes not-configured / explicitly-disabled / configured-but-unavailable) and which features degrade without it |
| Ensure the local REST backend is running (spawns |
| Manage that same backend: idempotent start (health-probes first, auto-moves to the next free port when 3777 is taken by a foreign process), status, and stop. Prints the active URL (with |
| Read-only memory hygiene lint: dangling/stale/duplicate/contradicted + machine-readable |
| Task-level memory benchmark: samples your own outcome history, measures lesson retrieval/injection rates; |
| Trend-over-time view of past |
| Archive stale memories based on access recency; also archives memories past their |
| Create a consistent point-in-time SQLite backup |
| Backup and restore — JSON to a file or a directory (writes |
| Mark memories as read (updates access_count) |
Integrations
Installing into your agents
MemVault ships native adapters for most agents — one shared store, per-host identity via MEMVAULT_AGENT_ID, four tiers (Tier 1/2/3 details below; per-client registration snippets in integrations/mcp-clients/).
Core packages & versions:
Package | Version | Install / Source |
| 0.7.2 | library dependency |
| 0.7.2 |
|
| 0.7.2 | npm registry (dsh Cordis plugin, below) |
Shipped plugins & versions — each bumps on its own schedule:
Plugin | Version | Distributed via |
Claude Code / Codex plugin bundle ( | 0.7.2 |
|
Gemini CLI extension ( | 0.7.2 |
|
Qoder plugin ( | 0.7.2 | in-repo manifest |
Obsidian plugin ( | 0.3.8 |
|
dsh Cordis plugin ( | 0.7.2 |
Tier 1 — one-command native plugins (memory injected by hooks; extraction opt-in where the host exposes lifecycle hooks):
Agent | Install | Recall | Extract |
Claude Code |
| ✅ SessionStart hook | ✅ Stop hook, enable with |
OpenCode | merge | ✅ system transform | ✅ on |
DeepSeek Harness (dsh) | built-in Cordis plugin | ✅ system prompt | ✅ turn-end |
Gemini CLI / Antigravity |
| ⚠️ rule context + tools | ❌ |
Codex CLI |
| ✅ SessionStart hook — approve the bundled hook once in | ✅ Stop hook — approve in |
⚠️ = the host has no injection hooks; recall is rule-driven (the agent calls session_start once) with the bundled canonical rule text.
Tier 2 — paste an MCP snippet. Strict-JSON registrations with per-host identities in integrations/mcp-clients/ (target paths in its README): Cursor · Windsurf · Cline/Roo · Continue · Zed · JetBrains AI/Junie · VS Code (Copilot Chat) · Claude Desktop.
Tier 3 — native manifests. Qoder (.qoder/rules/ + .qoder-plugin/ + a UserPromptSubmit hook template), Grok Build (grok plugin install dreamor/memvault --trust), the Hermes Python plugin (integrations/hermes/, pre_llm_call recall + extraction helper) and the pi extension (pi-extension/, declared by the root package.json pi manifest; pi install git:github.com/dreamor/memvault) ship in-repo; OpenClaw and Swival consume the generated root skills/ (also exported to .openclaw/skills/); Devin stays a manual recipe in integrations/README.md.
Tier 4 — instruction-only rule copies. Canonical text + scripts/gen-rule-copies.sh (parity-checked in CI) produce AGENTS.md/CLAUDE.md blocks, .cursor/rules/, .clinerules/, .kiro/steering/, Junie guidelines; memvault-cli sync --watch keeps them fresh from the store.
Any other MCP-speaking client (domestic or international, IDE plugin or CLI harness) connects with zero MemVault-side changes via the standard stdio config below — not individually verified; PRs adding a verified entry are welcome.
GUI surfaces are independent of agent installs: Web Dashboard (9 tabs) · Obsidian plugin (α — Vault sync + browse/capture) · MCP Proxy (transparent memory injection for any upstream server).
Architecture
┌────────────────────────────────────────────────┐
│ Clients (any MCP-compatible agent) │
│ ┌────────────┐ ┌────────┐ ┌─────┐ ┌────────┐ │
│ │ Claude Code│ │ Cursor │ │ dsh │ │ Others │ │
│ └────────────┘ └────────┘ └─────┘ └────────┘ │
└──────────────────┬───────────────────────────────┘
│ MCP (stdio / SSE / HTTP)
┌──────────────────▼───────────────────────────────┐
│ memvault-mcp (rmcp 3.1.1) │
│ ┌──────────────┐ ┌────────────────┐ ┌────────┐ │
│ │ 21 tools │ │ 2 Resources │ │ SSE │ │
│ │ + REST API │ │ + Auto-Inject │ │ Server │ │
│ └──────┬───────┘ └──────┬─────────┘ └────────┘ │
│ └────────┬───────┘ │
│ ┌───▼────────┐ │
│ │ Agent │ (Agent Registry │
│ │ Router │ type/tag filter) │
│ └───┬────────┘ │
├──────────────────┼────────────────────────────────┤
│ memvault-core │ │
│ ┌──────────┐ ┌─▼───────┐ ┌────────────┐ ┌───┐ │
│ │ storage │ │retrieval│ │ pipeline │ │sync│ │
│ │ SQLite │ │BM25+Vec │ │extractor │ │ │ │
│ │ │ │RRF+syn │ │dedup/decay │ │ │ │
│ │embed │ │onym │ │export/ │ │ │ │
│ │backfill │ │scoring │ │import │ │ │ │
│ └──────────┘ └─────────┘ └────────────┘ └───┘ │
└────────────────────────────────────────────────┘Project Status
MemVault is in beta. The Rust core (storage / search / injection) is CI-gated and stable; plugin adapters and GUI surfaces evolve faster. All configuration is environment-driven (see .env.example), and every change is recorded in CHANGELOG.md.
Testing
cargo test # ~1590 tests (full workspace)
cargo clippy --all-targets # zero warnings
cargo fmt --all -- --check # format check
cargo llvm-cov --workspace --all-features # CI gate: line ≥92% / region ≥90% / function ≥85%
cd dashboard && npm test # Vitest (UI + API layer)
bash scripts/e2e-release-check.sh # end-to-end, real binaries + real REST server
python3 docs/experiments/beam_adherence.py --dry-run --with-server # benchmark harness plumbingThe unit and integration suites are the primary gate, but e2e-release-check.sh
exists because several defects were visible only by running the built binaries
end to end — an edit that approved cleanly and changed no behaviour, a second
injection channel that bypassed the review gate, a provenance field dropped by the
reranker. All of them lived in the wiring between layers, where every layer's own
tests passed. It needs no LLM key and no embedding provider, so it is safe to gate
a release on, and CI runs it on every push.
Documentation
Doc | Content |
Product & architecture design | |
Installation guide (all platforms) | |
Agent-facing install guide — the target of the one-prompt Quick Start (install → register as MCP → verify recall) | |
Docker deployment | |
Deployment / health check / rollback runbook | |
Symptom → cause → fix troubleshooting guide | |
Historical H1–H7 acceptance and runtime evidence; | |
Release process — what CI automates (Linux/macOS binaries, Docker image, dashboard archive, Obsidian zip) vs. manual steps (Obsidian submission — no macOS signing needed) | |
Distribution channel map — automated vs. manual channels, required credentials, MCP registries, optional channels | |
Release history | |
Contribution guide | |
Security disclosures | |
Accessibility statement — commitment, supported environments, known limitations, how to report a barrier | |
Configuration template — single source of truth for every config key |
Contributing
🐛 Bugs: Issue Tracker
💡 Ideas: Feature Request
📖 Guide: CONTRIBUTING.md
🔒 Security: SECURITY.md
♿ Accessibility: ACCESSIBILITY.md
License
MemVault is released under the MIT License.
Available Tools
21 toolsadd_evidenceAIdempotent
Record evidence for a memory. relation="supports"/"contradicts" links evidence_id → memory_id (a memory supporting or contradicting it); relation="sourced_from" records memory_id's external provenance via source (URL/document). Writes one relation and returns its relation_id; an identical relation is rejected rather than duplicated. Contradictions accelerate the contradicted memory's decay; superseded or archived evidence stops counting. Requires agent auth when the agent has a registered key.
Inputs: relation (required), memory_id (required), source, api_key, +3 more.
confirm_readA
Confirm that one or more memories have been read by the agent. Increments access_count and sets last_read_at for the specified memory IDs; unknown IDs are skipped and the response reports how many rows were confirmed. Repeated calls increment the counters again (not idempotent). Requires agent auth when the agent has a registered key.
Inputs: memory_ids (required), api_key, agent_id.
delete_memoryADestructiveIdempotent
Soft-delete one memory by its ID: removes its live row, FTS entry, and cascaded evidence relations so it is no longer searchable or injected. A full snapshot is written to memory_history first; restore is available through the CLI (memvault restore), not through this MCP tool. Use forget_memory for an irreversible GDPR-style purge. Requires agent auth when the agent has a registered key; a second delete of the same ID returns NotFound.
Inputs: memory_id (required), api_key, agent_id.
extract_memoriesA
Extract structured memories from conversation text. mode="rule" (default) detects preferences, facts, and skills via keyword pattern matching. mode="llm" instead understands the full context (optionally pairing assistant_text) semantically — uses the configured LLM extraction provider, and degrades to rule-based extraction (reported via fallback_used/fallback_reason) when no provider is configured or the LLM call fails. Returns extracted items; with auto_save=true it also writes them through delta-write (near-identical memories are merged or skipped, not duplicated) and requires agent auth when the agent has a registered key. Use save_memory instead when you already know the exact memory to store. Invalid occurred_at is an error, never a silent drop.
Inputs: text (required), mode, api_key, agent_id, +5 more.
forget_memoryADestructiveIdempotent
Permanently erase (GDPR-style) one memory by id or a bulk set matched by criteria (namespace/namespace_prefix/source_agent_id/tag/memory_type/before_days). Unlike delete_memory, this also purges memory_history snapshots and any orphaned compliance rows, leaving only a content-hash audit entry in the forgotten-log — irreversible. dry_run defaults to true: call once to preview, then again with dry_run=false to execute. Priority::Must memories are excluded unless allow_must=true. Gated by the same per-agent API-key auth as delete_memory — there is no separate admin tier at the MCP layer.
Inputs: tag, reason, api_key, dry_run, +8 more.
get_compliance_reportARead-onlyIdempotent
Get a compliance report for injection sessions: with inject_session_id, followed/violated/pending counts plus compliance_rate for that session; without it, an aggregate summary (total_sessions, overall_rate, must_rate, recent_sessions) filtered by optional agent_id and limit (default 10). compliance_rate/overall_rate/must_rate are null when no real MUST verdict exists yet (all pending/unknown); null never means 100%. Use report_compliance to record follow/violation status — this tool only reads it.
Inputs: limit, api_key, agent_id, inject_session_id.
get_effectiveness_reportARead-onlyIdempotent
Get automatic effectiveness judgments for injected memories: useful/neutral/harmful/insufficient_context rates, judged automatically from record_outcome — independent of manual report_compliance. Optional agent_id filters the summary and limit defaults to 10. Read-only; returns JSON and does not change records.
Inputs: limit, api_key, agent_id.
get_memory_evidenceARead-onlyIdempotent
Get the raw-evidence chain a memory was distilled from (its L0 trace rows), plus its evidence profile. Read-only grounding: lets an agent quote the original session text and name its sources. Use add_evidence to write a new relation or source — this tool only reads the existing chain. Missing or pruned evidence yields an empty chain rather than a write; requires agent auth when the agent has a registered key.
Inputs: memory_id (required), api_key, agent_id.
import_skillsA
Import skills from a Markdown SOP document. Each #/## heading becomes a skill (trigger:/verification: metadata lines + list-item steps). Sections without steps are skipped. Imported skills enter the review inbox unless approve=true. Writes new skill memories; repeating the same import can create duplicates. Requires agent auth when the agent has a registered key.
Inputs: markdown (required), api_key, approve, agent_id, +2 more.
infer_outcomeA
Classify and record a task outcome from host-provided evidence rather than raw transcript text — for hosts whose event model doesn't produce a Claude-Code-shaped JSONL transcript (e.g. dsh/Cordis session events). Pass pre-computed friction counts and terminal state in evidence; this runs the same rule-floor-plus-optional-LLM-judge classification as the Claude Code Stop hook's outcome --infer, then records exactly like record_outcome. Returns status 'skipped' (not an error) when nothing was inferred — a clean session, below the friction threshold, or no task evidence at all. Repeated calls for the same session/evidence are deduped. Requires agent auth when the agent has a registered key.
Inputs: evidence (required), tags, api_key, agent_id, +4 more.
list_inboxARead-onlyIdempotent
List memories pending human review, sorted by created_at ascending (oldest first). Read-only. Supports an optional namespace and limit (default 20); there is no offset/pagination, so a full page silently truncates older pending memories. Requires agent auth when the agent has a registered key.
Inputs: limit, api_key, agent_id, namespace.
propose_memory_editA
Propose a text edit to an existing memory, for human review. Creates a PENDING memory carrying the edit; the target is left completely untouched and keeps injecting until a human approves. Approving it (review_memory action='approve') supersedes the target with the edited version; rejecting discards the proposal. old_text must occur exactly once — an ambiguous or absent anchor is an error, never a guess. field='content' (default) edits the body, field='instruction' edits the directive that injection renders. Use this instead of delete+save when you are correcting a memory you did not author: it keeps the current truth live until a person decides, and it cannot be used to silently rewrite a binding MUST.
Inputs: new_text (required), old_text (required), memory_id (required), field, +2 more.
record_outcomeA
Record the outcome of a task you just executed (episodic memory). Call this after finishing a task so past successes and failures can inform future sessions. Status must be 'success', 'failure', or 'partial'. Failures with a cause are reflected into lessons that get injected into similar future tasks. Repeated calls for the same session/outcome are deduped rather than creating a second episode. Use infer_outcome instead when the host supplies structured evidence rather than a transcript; use add_evidence to attach provenance to an existing memory. Returns status (recorded | duplicate), the episode id, and any distilled lesson. Requires agent auth when the agent has a registered key.
Inputs: task (required), status (required), tags, cause, +7 more.
report_complianceAIdempotent
Report compliance for a previous injection session returned by session_start. Call this to mark which injected memories were followed or violated, with optional evidence. Reports are processed item by item: a bad item is logged and skipped while the call still succeeds, so the response's updated/total counts must be checked rather than assuming all reports were stored. Requires a compliance-enabled server; no agent API key is required by this tool.
Inputs: reports (required), inject_session_id (required), api_key, agent_id.
review_memoryADestructive
Review or edit a memory. action='approve' marks it human-reviewed; action='edit' updates content/instruction and re-embeds or clears the stale vector (this also works on already-approved memories); action='reject' soft-deletes a pending memory and is rejected for already-approved memories (use delete_memory instead). Approved memories rank higher in future injections. Writes immediately; requires agent auth when the agent has a registered key.
Inputs: action (required), memory_id (required), api_key, agent_id, +2 more.
run_decayADestructive
Run a memory decay cycle: reduces decay_score for old memories and archives memories that fall below the threshold or whose expires_at valid-time bound has passed. MUST memories are exempt from score-based decay, but NOT from expiry — a MUST whose window has closed is a binding instruction that is no longer true. This is not purely reversible: if MEMVAULT_FORGET_AUTO_ENABLED=1, the same run also permanently forgets archived memories older than MEMVAULT_FORGET_RETENTION_DAYS (default 90); otherwise auto-forget is off. Requires agent auth when the agent has a registered key. Returns updated/archived/expired_archived/contradicted/harmful_flagged/auto_forgotten counts.
Inputs: api_key, agent_id.
run_dedupARead-onlyIdempotent
Scan for duplicate memories and report findings. Uses lexical text similarity (Jaccard) to detect near-duplicates in one namespace or all namespaces. Read-only: reports existing_id/new_content/similarity/action but does not merge or delete anything. Returns at most 20 duplicate findings.
Inputs: api_key, agent_id, namespace.
run_promoteADestructive
Run the promote pipeline: consolidates atomic L1 memories into L2 scenario summaries, and promotes stable L2 memories into L3 core persona rules. Requires L1 memories to exist; run run_dedup first so near-duplicates don't become separate scenarios. Source memories are archived to L0 after promotion (not deleted). A maintenance step, not a substitute for run_decay. Mutates the store, is not idempotent, and requires agent auth when the agent has a registered key. Returns promoted/consolidated/merged/source counts.
Inputs: min_l1, min_l2, api_key, agent_id, +1 more.
save_memoryA
Save a new memory. Memories are persistent user preferences, facts, episodes, or skills that should be recalled in future conversations. Embeddings are generated automatically for semantic search. Delta-write is on by default: near-duplicate saves are skipped and similar existing memories absorb the new content instead of a new row being created (status in the response: saved | merged | skipped). Pass force_insert=true to bypass. Writes persist immediately; requires agent auth when the agent has a registered key.
Inputs: content (required), tags, type, layer, +16 more.
search_memoryARead-onlyIdempotent
Search stored memories. mode defaults to 'hybrid' (keyword + vector via RRF); 'keyword' is text-only and 'semantic' is vector-only. Semantic/hybrid need an embedding provider — when embeddings are unavailable the query falls back to keyword and each result reports search_mode='keyword'. Supports namespace, type_filter, priority_filter, top_k (default 10), min_score, and optional expand_relations for one-hop relation context. TWO INDEPENDENT TIME AXES: as_of is valid-time — 'what did MemVault believe at T' — and returns each hit reconstructed to the state it held then, recalling from the historical index too so a memory reworded since T is still found by the words it had (keyword path only; such hits are tagged hist-kw#N); occurred_from/occurred_to filter event-time — 'what happened in March' — and never match memories saved without a date. They answer different questions and are not interchangeable. Read-only; does not mutate memories.
Inputs: query (required), mode, as_of, top_k, +9 more.
session_startA
Start an agent session. Returns relevant memories filtered by agent identity, formatted as MUST/REF instructions ready for injection into the conversation context; overflow memories are summarized with a hint to use search_memory for details. If this agent's canonical inject channel is not MCP, returns a skip explanation instead of injecting. When compliance tracking is enabled, records the injected memories and returns inject_session_id in structured_content for a later report_compliance call. Not read-only; requires agent auth when the agent has a registered key.
Inputs: api_key, project, agent_id, agent_type, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 21 tools
Most tools have a distinct role, and the descriptions explicitly clarify near-neighbors such as save_memory vs extract_memories, delete_memory vs forget_memory, and record_outcome vs infer_outcome. However, multiple pairs overlap by design, including propose_memory_edit vs review_memory edit, the two compliance/effectiveness reports, and the three maintenance tools, so an agent must read carefully to select correctly.
The set mostly follows a verb_noun pattern: save_memory, search_memory, delete_memory, get_compliance_report, import_skills, and run_decay. The main deviation is session_start, which reverses the order and mildly breaks the otherwise consistent convention.
At 21 tools, the surface is heavy for a memory server, though the domain is broad and includes lifecycle, extraction, review, evidence, compliance, outcomes, skills, and maintenance. Several adjacent reporting and maintenance tools could likely be consolidated without losing core capability.
The set covers the main memory lifecycle: save/search/delete/forget, review and edit proposals, evidence, session injection, outcomes, compliance, and maintenance. Minor gaps remain, notably restore being CLI-only and some list/report operations lacking pagination or fuller management surfaces.
Maintenance
Related MCP Connectors
An MCP memory server. One memory your agents share — across models, devices and apps.
Hosted memory for AI agents over MCP. One memory shared by all your agents.
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables persistent, hybrid, local memory for LLM agents, with vector + BM25 search, knowledge graph, and policy-driven retention, providing token-budgeted context injection for AI assistants.MIT
- AlicenseNot gradedqualityBmaintenanceA vendor-independent memory layer MCP server that enables multiple LLMs and AI agents to share and persist personal memories, knowledge, and context across sessions, with support for full-text search and tagging.ISC
- AlicenseNot gradedqualityBmaintenanceProvides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.3MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted memory server that gives AI agents a shared, persistent second brain, enabling verbatim storage, hybrid semantic/keyword retrieval, and a synthesized wiki layer through MCP tools.2MIT