Memory Vault runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 10 Sep 2026.
Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
What the code does
We read the source, 19 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return Path("/.dockerenv").exists()
result = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Memory Vault
same job, measured the same wayEnterprise PostgreSQL MCP server with NL queries, hybrid search (pgvector+BM25), and web UI
Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres.
Self-hosted MCP memory server: a typed knowledge graph on Postgres 16 and pgvector.
Embedded memory for AI agents with SQLite, pgvector, and Neo4j graph search.
Similarity search, hybrid search, and index management for pgvector-backed PostgreSQL tables
Local-first graph memory for AI assistants with SQLite, semantic search, and MCP tools.
Local-first AI memory cartridge with persistent MCP memory for Claude via SQLite FTS5.
Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
Memory Vault — questions
Answers built from our own checks of this server.