Memory Vault

Distribution release — Memory Vault now ships as two Docker images:

• ghcr.io/mihaibuilds/memory-vault:1.0.4 — the existing all-in-one image (API + dashboard + MCP)
• ghcr.io/mihaibuilds/memory-vault-mcp:1.0.4 — new — thin MCP-only image for connecting to an external Postgres+pgvector

No code changes, no behavior changes for existing users. Drop-in replacement for v1.0.3.

What's new

memory-vault-mcp image

A second Docker image that ships ONLY the MCP stdio server. Connects to an external Postgres+pgvector via env vars (DB_HOST, DB_PORT, DB_NAME, DB_USER, DB_PASSWORD). Intended for:

• Direct use in mcp.json configurations where you already have Postgres running elsewhere
• MCP catalog registries (official MCP registry + Docker MCP Toolkit submissions coming next)
• Integration in larger Docker Compose setups where Postgres is shared with other services

Use it

docker pull ghcr.io/mihaibuilds/memory-vault-mcp:1.0.4

Or in Claude Desktop mcp.json:

{
  "mcpServers": {
    "memory-vault": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "DB_HOST=host.docker.internal",
        "-e", "DB_PORT=5432",
        "-e", "DB_NAME=memory_vault",
        "-e", "DB_USER=memory_vault",
        "-e", "DB_PASSWORD=memory_vault",
        "ghcr.io/mihaibuilds/memory-vault-mcp:1.0.4"
      ]
    }
  }
}

The existing all-in-one image continues to work exactly as before — docker compose up from the published docker-compose.yml is unchanged.

Upgrade existing deployments

docker compose pull
docker compose up -d

170 tests passing in CI on Python 3.14 + Postgres 16 + pgvector. Both images built multi-arch (amd64 + arm64).

Full changelog

Compare: v1.0.3...v1.0.4