Local-first email and calendar inbox for AI agents
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"chronos-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Chronos — agent-inbox [](https://opensource.org/licenses/MIT) [](https://www.python.org/downloads/) Local-first email and calendar inbox for AI agents. Syncs Gmail and Google Calendar into a single queryable SQLite database and exposes all data through an MCP server. ## Features - Sync multiple Gmail and Google Calendar accounts into one SQLite database - Full-text search via FTS5 with BM25 relevance ranking (messages, events, attachment names) - MCP server via `chronos --mcp-stdio` (stdio transport, no port required) - HTTP REST API at `localhost:7070` for direct queries - Read-only SQL interface via `POST /v1/query` - Optimistic event writes with provider-wins conflict resolution - Incremental sync with historyId (Gmail) and syncToken (Calendar) - ULID primary keys, WAL mode, no cloud dependencies at query time ## Installation ```bash pipx install chronos-mcp ``` Or from source: ```bash git clone https://github.com/CourtimusPrime/chronos.git cd chronos pip install -e . ``` ## Setup Run the interactive walkthrough for detailed step-by-step instructions: ```bash chronos --walkthrough ``` This prints the full guide in the terminal and saves it to `~/.chronos/WALKTHROUGH.md` for future reference. ### Quick start **1. Google Cloud Console** - Create a project at [console.cloud.google.com](https://console.cloud.google.com) - Enable **Gmail API** and **Google Calendar API** - Configure OAuth consent screen (External, Testing mode) — add your Google account as a Test User - Add scopes: `https://mail.google.com/` and `https://www.googleapis.com/auth/calendar` - Create an OAuth client ID — **Application type: Web application** - Add authorized redirect URI: `http://localhost:9004/callback` - Download the credentials JSON > Desktop App credentials (`"installed"` JSON shape) are **not supported** — > Chronos uses the `https:…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.