Memory Vault
Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
Verdict not yet evaluated for this tool. The hybrid eval runs adversarial cases first; coverage rolls out as the corpus expands. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: hybrid eval, four-state verdict, honest limits.
{
"mcpServers": {
"memory-vault": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mihaibuilds/memory-vault-mcp:1.0.6"
],
"env": {
"DB_HOST": "<db_host>",
"DB_PORT": "5432",
"DB_NAME": "memory_vault",
"DB_USER": "memory_vault",
"DB_PASSWORD": "<your-db_password>"
}
}
}
}DB_HOSTHostname of the Postgres+pgvector instance Memory Vault connects to (e.g. 'host.docker.internal' when Postgres runs on the host, 'localhost' when running natively, or the service name when both run in compose)
DB_PORTPostgres port
DB_NAMEPostgres database name
DB_USERPostgres user with read/write access to the memory vault database
DB_PASSWORDPostgres password for DB_USER
Database MCP server for MySQL, MariaDB, PostgreSQL & SQLite with PII redaction and write-prevention
Manage Supabase projects end to end across database, auth, storage, realtime, and migrations. Moni…
Explore your Messages SQLite database to browse tables and inspect schemas with ease. Run flexible…