mimir-memory-mcp

# Mimir **Structured memory server for AI assistants.** Mimir stores what an assistant needs to keep: work (threads, tasks, reminders) and knowledge (rules, facts) anchored to the work it is about. Multi-user, scope-based access control, tiered context loading, keyword search, a full audit trail. The **HTTP API is the contract**. The [MCP](https://modelcontextprotocol.io/) surface is a generated adapter over the same operation registry — every operation exists on both, and neither can quietly grow one the other lacks. Named after [Mímir](https://en.wikipedia.org/wiki/M%C3%ADmir), the Norse keeper of the Well of Wisdom. ## 1.0 is a clean break 1.0 does not read a 0.x database. New schema, new API, new database file; the server refuses a pre-1.0 file at boot and names the way across: ```bash mimir-mcp migrate --from ./old-mimir.db --to ./mimir.db ``` The migration is a one-time move into a *new* file — dry-runnable, with judgement queues for what does not map cleanly. The 0.x tool names and session lifecycle (`start_session`, `end_session`, `set_context`, …) are gone: nothing opens, closes or resumes — every call carries its own authority, and re-reading replaces remembering. ## Quick Start ### pip ```bash pip install mimir-memory-mcp # write seed.sql — your principal, scope, membership (see Provisioning below) MIMIR_DB_PATH=./mimir.db MIMIR_SEED_FILE=./seed.sql MIMIR_PORT=8100 mimir-mcp ``` ### Docker ```bash cp seed.sql.example data/seed.sql # edit: your principal and scope docker compose up -d --build # compose provides MIMIR_DB_PATH and MIMIR_SEED_FILE ``` `scripts/setup.sh` walks the same steps with a health check. ### From Source ```bash git clone https://github.com/jimmy-larsson/mimir.git cd mimir pip install -e ".[dev]" cp seed.sql.example seed.sql # edit: your principal and scope MIMIR_DB_PATH=./mimir.db MIMIR_SEED_FILE=./seed.sql mimir-mcp ``` ## Configuration | Environment Variable | Default | Description | |--------------…