
openchronicle-mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv3.0.0.dev1Updated Oct 27, 2026
Memory database for LLM agents — persistent semantic + keyword memory, project namespacing, served o
Overview
Self-hosted memory database for LLM agents, giving an assistant persistent semantic and keyword memory scoped to projects.
- What you can do
- Save decisions, milestones and rejected approaches as memories that survive new sessions and context compression
- Search memories with hybrid full-text and semantic retrieval, and check server health
- Scope memory to individual projects so context does not leak between workstreams
- Onboard a git repository by clustering commits and returning summaries ready for memory ingestion
- When to use it
- Useful when you want an assistant to remember decisions and rationale across conversations, or to seed long-term memory from an existing codebase, while keeping the data on your own hardware.
- Requirements
- Runs as a local process; the README installs from source with pip and the oc CLI (oc init, oc serve), or as a Docker container. The server binds 127.0.0.1:8000 by default and is reached over HTTP at /mcp. In a container, OC_API_HOST must be set to 0.0.0.0, and non-localhost hostnames need OC_MCP_ALLOWED_HOSTS. An embedding provider is used for semantic search.
Installation
In SourceWeft
- Open openchronicle-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
OpenChronicle
[code confidence] · claude-fable-5 · 2026-08-30 · details
[License: AGPL-3.0] [Docker] [Python 3.14+]
A memory database for LLM agents. Persistent semantic + keyword memory, project namespacing, git-onboard, served over HTTP REST and MCP from a single ASGI process. Runs on your hardware.
What it does
- Persistent memory across sessions. Save decisions, milestones, and rejected approaches that survive context compression and new conversations. Retrieve them with hybrid full-text and semantic search via Reciprocal Rank Fusion.
- Project namespacing. Memory is scoped to projects, so context for one workstream doesn't leak into another.
- Git onboarding. Clone a repo, cluster commits by relatedness, return summaries ready for memory ingestion. Seeds long-term memory with the WHY behind existing code.
- One process, two transports. FastAPI hosts both the REST surface
(
/api/v1/*) and the MCP streamable-HTTP transport (/mcp) on the same port. Single container, single port mapping, single healthcheck. - Embedding-failure degradation. When the embedding provider goes
down, search degrades cleanly to FTS5-only and surfaces the
degraded state via
/api/v1/healthand the MCPhealthtool. Backfill catches up when the provider returns; the static/healthendpoint remains a minimal liveness probe. - Optional operational metrics. Released images (since v3.4.0) include
the bounded Prometheus recorder and guarded
/metricsendpoint, off by default. Opt in withOC_METRICS_ENABLED=true; enabling it in production stays subject to the performance gates. See the metrics configuration and the optional local monitoring runbook. - Schema migration framework. Versioned
.sqlmigrations with savepoint atomicity. Re-runs are idempotent. Future schema changes drop in asNNN_<slug>.sqlfiles. - Verified online backups. Uses SQLite's online backup API; each
nightly snapshot is published with a verified manifest in
OC_BACKUP_DIR, and one that fails verification is quarantined. Backup-before-destructive policy: vacuum runs a backup first as part of the same job. Integrity-check failures trigger emergency backups. - Optional encrypted offsite copies. A nightly job encrypts the newest snapshots with age and copies them to any rclone remote, append-only. See cloud_backup.md.
What it isn't
- Not a conversation engine. v3 has no LLM. Use Claude Code, Goose, Open WebUI, etc. via the MCP server.
- Not multi-tenant. Single user. Bearer-token auth via
OC_API_KEYis supported but optional — disabled by default for trusted-LAN deployments. Seedocs/configuration/security_posture.mdfor the when-to-enable guidance. - Not a cloud sync layer. The DB lives on your hardware. Backups go to
a local backup directory and, optionally, encrypted to a cloud remote,
as backup only. Cross-device sync isn't built in
(
docs/design/0001-cloud-backup.md).
By design.
Install
From source:
The default oc serve binds 127.0.0.1:8000. Override with
--host/--port or OC_API_HOST/OC_API_PORT.
Docker (single container, NAS-friendly):
OC_API_HOST=0.0.0.0 is required in a container — the app default
binds container-loopback, which the port mapping can't reach. To call
the server by anything other than localhost (a NAS hostname, a LAN
IP), also set OC_MCP_ALLOWED_HOSTS=your-host:* or every request gets
a 421 (see
env_vars.md).
For a Portainer stack on a NAS, use the docker-compose.nas.yml at
the repo root. It needs three things first: OC_TAG set to a release tag
(there is no :latest fallback), the data volume created once
(docker volume create openchronicle-mcp_oc-data; the compose never
creates it, so a missing volume fails the deploy instead of starting
empty), and the host exports directory created and owned by uid 1000. The
file's header comments list every variable.
Quickstart
Or do the same via MCP — register the server with Claude Code:
Then ask Claude to call memory_save and memory_search.
Architecture
Hexagonal: domain/ (pure types + ports) → application/ (use cases,
services) → infrastructure/ (SQLite, embedding adapters, the
maintenance loop). Driver-side adapters in interfaces/ host the
HTTP, MCP, and CLI surfaces.
See docs/architecture/ARCHITECTURE.md for the full layout.
Documentation
docs/architecture/ARCHITECTURE.md— layout, schema, ASGI designdocs/architecture/MAINTENANCE.md— maintenance loop + degradation policydocs/cli/commands.md—ocsubcommand referencedocs/configuration/env_vars.md— environment variablesdocs/configuration/config_files.md—core.jsonschemadocs/configuration/security_posture.md— security modeldocs/integrations/mcp_client_setup.md— register the MCP serverdocs/integrations/mcp_server_spec.md— MCP tool surfacedocs/api/STABILITY.md— versioning + deprecation policydocs/design/README.md— proposed designs and comparative repository reviews
Development
Dependencies are locked in uv.lock, which CI and the Docker image
install from; run uv lock after changing anything in [project] in
pyproject.toml, including the version.
The architecture is enforced by tests:
tests/test_hexagonal_boundaries.py— domain/application/infrastructure layeringtests/test_architectural_posture.py— core agnostic of MCP SDKtests/test_no_secrets_committed.py,tests/test_no_soft_deprecation.py— repo hygiene
License
Copyright (C) 2025-2026 CarlDog
AGPL-3.0. This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. It is distributed WITHOUT ANY WARRANTY; see the license for details.
The copyright line lives here rather than inside LICENSE: that file is
the AGPL text verbatim, and the <year> <name of author> placeholders in
its closing appendix are the license's own instructions for what to put
in your source files — not blanks to fill in. Editing them would modify
the license text itself.
Source: README.md at commit bc0658e
Tools
0Version history
1- v3.0.0.dev1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
