Docker Compose
Docker Compose is the supported way to run Remem 0.5. The Community release builds one Go service containing the HTTP API, MCP endpoint, Pebble storage, local embeddings, search indexes, lifecycle, and background jobs.
Start the Community release
Section titled “Start the Community release”git clone https://github.com/remem-org/remem-community.gitcd remem-communitycp .env.example .envmkdir -p ./remem-datasudo chown 10001:10001 ./remem-datadocker compose up --build -dSet REMEM_SERVER_API_KEY in .env before starting. The default Compose file
bind-mounts REMEM_DATA_DIR to /var/lib/remem, so the corpus remains visible
on the host and is not removed by docker compose down -v.
Verify the service
Section titled “Verify the service”docker compose pscurl http://localhost:4545/api/v1/readyAuthenticated endpoints use the key from .env:
curl http://localhost:4545/api/v1/memories \ -H "Authorization: Bearer $REMEM_SERVER_API_KEY"The HTTP API and Streamable HTTP MCP endpoint are served on port 4545.
Configuration
Section titled “Configuration”Remem runs with built-in defaults. To override them, copy
config/remem.toml, edit it, and pass it to the server with the --config
option or the corresponding environment variables. See
Configuration for storage, search, lifecycle,
job, tenant, and metrics settings.
Updating
Section titled “Updating”git pulldocker compose up --build -dPebble keeps the corpus durable across container restarts. Back up the host
data directory before upgrades and use remem-admin for portable export,
import, verification, and index maintenance.
MCP over stdio
Section titled “MCP over stdio”The remem-mcp companion binary connects local clients such as Claude Desktop
to the running /mcp endpoint. For clients that support Streamable HTTP, use
http://localhost:4545/mcp directly.
