OpenChronicle
Persistent memory database for LLM agents with hybrid semantic and keyword search, project namespacing, and MCP/REST interfaces.
README
OpenChronicle
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
/health. Backfill catches up when the provider returns. - Schema migration framework. Versioned
.sqlmigrations with savepoint atomicity. Re-runs are idempotent. Future schema changes drop in asNNN_<slug>.sqlfiles. - Atomic online backups. Uses SQLite's online backup API. Backup-before-destructive policy: vacuum runs a backup first as part of the same job. Integrity-check failures trigger emergency backups.
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 directory next to it. Cross-device sync isn't built in (see V3_PLAN.md open question 12 for the design sketch).
By design.
Install
From source:
pip install -e ".[mcp,openai]"
oc init
oc serve
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):
docker run --rm \
-p 8000:8000 \
-v $(pwd)/data:/app/data \
-v $(pwd)/config:/app/config \
ghcr.io/carldog/openchronicle-mcp:latest
For a Portainer stack on a NAS, use the docker-compose.nas.yml at
the repo root.
Quickstart
# Bootstrap the runtime tree
oc init
oc init-config
# Create a project
PROJECT_ID=$(oc init-project "my-project")
# Save your first memory
oc memory add "Decision: SQLite for storage; AGPL for license" \
--project-id $PROJECT_ID --tags decision
# Search it
oc memory search "storage decision" --project-id $PROJECT_ID
Or do the same via MCP — register the server with Claude Code:
claude mcp add --scope user --transport http openchronicle \
http://127.0.0.1:8000/mcp
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 policy
Development
pip install -e ".[dev,mcp,openai,ollama]"
pre-commit install
pytest
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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.