Personal memory server
Self-hosted devices, actors, operation envelopes, provenance edges, routed shard selection, synchronization receipts, revocation, and quarantine.
03THE PLATFORM
You can stop at the layer you need. semantic-memory owns memory quality. semantic-memory-mcp exposes it to one local agent. Mnemes adds the self-hosted server, multi-device identity, routing, and synchronization metadata.
Self-hosted devices, actors, operation envelopes, provenance edges, routed shard selection, synchronization receipts, revocation, and quarantine.
Stdio and loopback HTTP, runtime-discovered tools, bounded profiles, witnessed search, replay, graph traversal, authority decisions, and maintenance boundaries.
SQLite authority, hybrid retrieval, embeddings, graph, bitemporal state, provenance, receipts, replay privacy, integrity, and reconciliation.
01 / THE ENGINE
The memory engine owns durable storage and retrieval mechanics. It does not own claim truth, action permission, MCP transport policy, or automatic activation of every research feature.
SQLite content, raw f32 embeddings, temporal fields, lineage, authority records, and durable receipts.
FTS5/BM25 plus dense candidates, weighted reciprocal-rank fusion, deduplication, diversity, and explicit state visibility.
Current, historical, and superseded fact views with valid time separated from recorded time.
Semantic, temporal, causal, and entity relationships with invalidation instead of silent deletion.
Capability-gated append, supersession, redaction, forgetting, export, replay, and origin revocation.
Integrity checks and reconciliation rebuild derived state from canonical SQLite authority.
02 / THE PROTOCOL
The running server's tools/list response remains the source of truth. Build features and runtime profile both affect what a client can actually call.
Witnessed recall, replay, and separate assertion/action authority decisions. Designed for the narrowest autonomous surface.
Search, fact reads, graph paths, conversations, namespaces, receipts, and stats without device administration.
Mutation, imports, lifecycle, maintenance, administration, and experimental tools. Treat discovery as runtime evidence, not README promise.
03 / NINE AGENT HOSTS
Agent Memory Kits are a complete single-device starting point, not a reduced demo. They distribute semantic-memory-mcp into hook-tier and context-tier hosts; Mnemes is added only when a server and cross-device memory boundary are wanted.
Recall, primer, capture, and compaction lifecycle hooks.
MCP configuration, Python hooks, prompts, and memory skills.
Hooks, commands, and skills around one canonical store.
MCP plus project-local memory context rules.
MCP and deterministic context-injection guidance.
MCP plus project or user-scoped rules.
MCP tools with host-native instruction files.
MCP registration and shared context commands.
MCP registration and local memory rules.
04 / COMPRESSION WITH AN ESCAPE HATCH
Canonical memory stays exact. Compressed tiers make candidate retrieval smaller and more efficient. Approximate scores find candidates; authoritative f32 scoring decides the final order.
Durable content and exact vectors remain the authority.
Derived artifacts narrow the working set under explicit policy.
Final ranking returns to authoritative vectors before visibility filters.
Registry and repository values are requested from public APIs in your browser. If crates.io is unavailable, versions and downloads use only the bundled snapshot observed Jul 16, 2026 and are labeled as such. Missing GitHub values remain unavailable; nothing is inferred from a different source.