Memory Vault MCP Server

Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.

Local serverstdio

What is the Memory Vault MCP Server?

Memory Vault is an MCP integration. Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.

Packages and local setup

The published oci package is ghcr.io/mihaibuilds/memory-vault-mcp:1.6.0. Its declared MCP transport is stdio.

The package declares DB_HOST (required): Hostname 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_PORT (required): Postgres port; DB_NAME (required): Postgres database name; DB_USER (required): Postgres user with read/write access to the memory vault database; DB_PASSWORD (required): Postgres password for DB_USER.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.6.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related databases MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
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)Yes
DB_PORTPostgres portYes
DB_NAMEPostgres database nameYes
DB_USERPostgres user with read/write access to the memory vault databaseYes
DB_PASSWORDPostgres password for DB_USERYes