Chronicle

Name: Chronicle
Author: aniketxdey

by aniketxdeyversion 0.3.0i★ –iRuns on your computer

Registry nameio.github.aniketxdey/chronicle

Install

Overview

Description from the maker (original English)

Local screen and activity knowledge graph, served as context to computer-use agents.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CHRONICLE_HOME, CHRONICLE_DISABLE_CAPTURE

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "chronicle": {
      "command": "uvx",
      "args": [
        "chronicle-context",
        "mcp"
      ],
      "env": {
        "CHRONICLE_HOME": "your-value",
        "CHRONICLE_DISABLE_CAPTURE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add chronicle --env CHRONICLE_HOME=your-value --env CHRONICLE_DISABLE_CAPTURE=your-value -- uvx chronicle-context mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chronicle": {
      "command": "uvx",
      "args": [
        "chronicle-context",
        "mcp"
      ],
      "env": {
        "CHRONICLE_HOME": "your-value",
        "CHRONICLE_DISABLE_CAPTURE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chronicle": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "chronicle-context",
        "mcp"
      ],
      "env": {
        "CHRONICLE_HOME": "your-value",
        "CHRONICLE_DISABLE_CAPTURE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CHRONICLE_HOME env
Folder for the database and screenshots (default ~/.chronicle)
CHRONICLE_DISABLE_CAPTURE env
Set to 1 so this process serves context but never records

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account aniketxdey, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5679 servers in this category
Published to the registry more recently than 92% of the other 5679 servers in this category
Basic checks equal to or better than 100% of the other 5679 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Chronicle safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Chronicle

Record your screen and system events on your computer, write context files and workflows from them, and build them into LLM harnesses for any task. Any AI can use a harness over MCP or as downloaded files.

The full documentation covers the app, every command, and the API.

An agent usually starts each task with no knowledge of your computer. It doesn't know your ticket, your open file, or your last search, so you paste that context by hand. Chronicle keeps that memory on your computer and lets the agent request it:

Continue your work. "Finish the Acme export" works because the agent can see export.ts, the status of PR 882, and the Notion spec.
Teach by showing. Record a task once. The agent gets the apps, pages, and steps in order.
Use tools without MCP. Download a harness as a .zip or one Markdown file for ChatGPT, Claude Projects, NotebookLM, Neo4j, or a RAG pipeline.

Chronicle stores everything in ~/.chronicle, with no account and no telemetry. See Privacy for what leaves your computer.

Quick start

Chronicle needs Python 3.10 or newer. macOS is the main platform, and Linux (X11) and Windows support is best effort.

These commands load a synthetic workday, so Chronicle records nothing.

uv tool install --python 3.12 "chronicle-context[graph]"

chronicle demo chronicle context "finish the Acme export"

chronicle context prints the Markdown that the get_context MCP tool returns. The sample output starts like this:

# Computer context (Chronicle)

Task: finish the Acme export Window: the most recent 2h of history.

What you were doing

14:55-15:31 meeting Acme weekly · Jordan Hale (36m)
15:34-16:24 writing customer emails · export spec (50m)
16:28-16:48 coding export.ts · asking Priya (20m)

On screen now

Chrome · Checks · PR 882 (frame 18)
URL: https://github.com/northwind/billing/actions

To open the app, connect an agent, and record your own work:

chronicle serve

chronicle mcp install cursor chronicle doctor chronicle record 30m --label "file an expense report"

The app runs at http://127.0.0.1:3030. chronicle mcp clients lists every client.

Permissions and tools

Platform	What Chronicle needs
macOS	Screen Recording and Accessibility for the app that runs Chronicle. Local sources also need Full Disk Access
Linux	X11, a window manager, `xdotool`, and `xprop`. Wayland sessions aren't supported for window tracking
Linux screenshots	One of `grim`, `gnome-screenshot`, `scrot`, or ImageMagick `import`
Linux clipboard and idle time	`xclip` or `wl-paste`, and `xprintidle`
Windows	Nothing extra. Chronicle uses user32 and PowerShell
OCR, optional	`brew install tesseract` or `apt install tesseract-ocr`

On macOS, the app that runs Chronicle is your terminal or the MCP host, such as Claude Desktop or Cursor. Add it under System Settings › Privacy & Security, then quit and reopen it. Closing its windows isn't enough.

How it works

Record. A session runs for a set time, such as 90s, 30m, or 2h, or until you stop it. Every 5 seconds by default, Chronicle samples the front app, its window, and the browser URL. When something changes, and at least every 30 seconds, Chronicle also takes a screenshot and reads screen text. Chronicle never records keystrokes, and it skips password managers, System Settings, and private browser windows.

Read sources. Under Privacy & Sources, you can also turn on Apple Mail, Calendar, iMessage, WhatsApp, browser history, folders, and AI tool logs. Every source starts off.

Build the graph. Each session gets its own graph. Nodes include apps, pages, files, tickets, PRs, people, topics, and tasks. Every node and edge records its time and its source frames, so an agent can cite its evidence. The all-history graph combines the sessions, and older sessions count less.

Write. With a model set up, Chronicle names the graph's work, then writes context files and workflows when a recording ends. Without a model, Chronicle runs offline and builds plain context files from the evidence.

Serve. Agents read everything over MCP.

Level	What it is	Example
Harness	Everything an agent needs for a whole line of work	Recruiting
Context file	General guidance for one kind of session	Researching job companies
Workflow	A short procedure for one specific job	Customizing resume bullets

Connect an agent

Local clients

chronicle mcp install adds Chronicle to a client's config and keeps a .chronicle-backup copy of the old file. chronicle mcp config prints the snippet and writes nothing.

Client	Command
Claude Desktop	`chronicle mcp install claude-desktop`
Claude Code	`chronicle mcp install claude-code`
Cursor	`chronicle mcp install cursor`
VS Code (Copilot agent mode)	`chronicle mcp install vscode`
Windsurf	`chronicle mcp install windsurf`
OpenAI Codex CLI	`chronicle mcp install codex`
Gemini CLI	`chronicle mcp install gemini-cli`
Cline	`chronicle mcp install cline`
LM Studio	`chronicle mcp install lm-studio`
Zed	`chronicle mcp config zed`
Continue	`chronicle mcp config continue`
Goose	`chronicle mcp config goose`

Restart the client after an install. Only one Chronicle process captures at a time, so an agent can call start_recording without chronicle serve. chronicle mcp --no-record turns that off.

Packaged installs

Packaged installs need only uv.

claude plugin marketplace add aniketxdey/chronicle

claude plugin install chronicle@chronicle

gemini extensions install https://github.com/aniketxdey/chronicle

MCP Registry clients can search for io.github.aniketxdey/chronicle.

Hosted agents and APIs

Hosted agents need a public HTTPS URL. Anyone with the URL that these commands print can read your Chronicle data. Stop the tunnel when you finish.

export CHRONICLE_TOKEN=$(openssl rand -hex 16)

export CHRONICLE_PUBLIC_URL=https://YOUR-TUNNEL-HOST chronicle serve & cloudflared tunnel --url http://127.0.0.1:3030 echo "$CHRONICLE_PUBLIC_URL/mcp/$CHRONICLE_TOKEN"

chronicle mcp config prints a starting point for chatgpt, openai-api, anthropic-api, gemini-api, and http. Provider model names and beta flags change often, so check each provider's MCP documentation. The examples folder has longer scripts.

Files

The harness editor exports a .zip or one Markdown file. Each context file and workflow has Download .md. Each graph downloads as JSON, text, GraphML, or Cypher.

MCP tools

Tool	What it does
`list_harnesses`, `get_harness`, `read_harness_file`, `search_harness_graph`	Read a harness, its files, and its graph engine
`get_context_file`, `get_workflow`, `get_graph`	Read one context file, workflow, or graph
`get_context`	A context pack for a task, with an optional preset
`search_history`	Full-text search over screen text, events, transcripts, and memories
`query_graph`, `get_entity`, `graph_summary`	Find nodes, read their evidence, and get graph totals
`list_tasks`, `activity_summary`, `list_meetings`	Timelines and summaries
`get_frame`	One frame, optionally with its screenshot
`start_recording`, `stop_recording`, `list_sessions`	Record a demonstration, and list recordings
`rebuild_graph`, `tune_graph`	Rebuild a graph, or refine it with your model
`graph_review`, `graph_apply`	The connected agent curates the graph, with no Chronicle model
`search`, `fetch`	The interface that ChatGPT connectors and deep research expect

The server also has resources, such as chronicle://context/current, and two prompts: use_my_computer_context(task) and learn_from_recording(session_id). The MCP reference lists them all.

App, API, and CLI

chronicle serve runs the app at http://127.0.0.1:3030:

Page	What it does
Knowledge	Shows the graph of all your history, a chat, and your recordings. The chat can propose something to build, and builds nothing until you press its button
Harnesses	Builds a harness in five steps, then edits it by hand or by chat
Contexts	Holds general guidance for one kind of session
Workflows	Holds short procedures for one job
Integrations	Connects MCP clients and exports files
Privacy & Sources	Controls what Chronicle reads besides recordings
Settings	Controls capture, retention, and models

The REST API has interactive documentation at http://127.0.0.1:3030/docs. The CLI reference and REST reference list every command and route. The CLI has no harness commands.

Configuration

Variable	Default	Meaning
`CHRONICLE_HOME`	`~/.chronicle`	Database, screenshots, and lock file
`CHRONICLE_HOST`, `CHRONICLE_PORT`	`127.0.0.1`, `3030`	Where `chronicle serve` listens
`CHRONICLE_TOKEN`	Unset	Require this token on the HTTP API and MCP
`CHRONICLE_PUBLIC_URL`	`http://127.0.0.1:3030`	Base URL for links and remote client snippets
`CHRONICLE_DEMO=1`	Off	Load the sample workday into an empty database on start
`CHRONICLE_DISABLE_CAPTURE=1`	Off	Never record from this process
`CHRONICLE_HALF_LIFE_HOURS`	`72`	How fast older recordings count less in All history. `0` or `off` disables it
`CHRONICLE_LLM`	Unset	`openai`, `anthropic`, `gemini`, `openrouter`, `local`, or `off`
`CHRONICLE_LLM_MODEL`	Provider default	Model for the provider named by `CHRONICLE_LLM`
`CHRONICLE_LLM_BASE_URL`	`http://localhost:11434/v1`	Endpoint for the local provider

Chronicle reads these variables when a process starts. Settings in the app holds capture interval, idle threshold, screenshots, OCR, clipboard, redaction, and retention.

Models

A model is optional. Open Settings › Model, add a key, and press Use.

Provider	Default model	Key from the environment
OpenAI	`gpt-4.1-mini`	`OPENAI_API_KEY`
Anthropic	`claude-sonnet-5-5`	`ANTHROPIC_API_KEY`
Google Gemini	`gemini-2.5-flash`	`GEMINI_API_KEY`
OpenRouter	`openai/gpt-4.1-mini`	`OPENROUTER_API_KEY`
Local (Ollama, LM Studio)	You choose	Not needed

A key can also be in a .env file in ~/.chronicle or the current directory. A .env file never overrides a variable that is already set. Your choice in Settings overrides CHRONICLE_LLM, except CHRONICLE_LLM=off, which turns models off whatever Settings says.

Workflows, harness chat, and context file names use tool calls, so choose a model that supports them. Small local models often fail at these tasks.

Privacy

Recordings, screenshots, source items, and graphs stay in ~/.chronicle. Data leaves your computer in these cases:

MCP clients: a connected agent receives the tool results it requests.
Models: a cloud model receives window titles, URLs, system events, redacted screen text, and matching source items.
Tunnels: anyone with your URL and token can read your data.
Cloud sources: a provider sees the requests that Chronicle makes to it.

Redaction applies to text only. Screenshots keep whatever was on screen. [PRIVACY.md](https://github.com/aniketxdey/chronicle/blob/main/PRIVACY

Only the beginning is shown; read the rest in the repo

Chronicle

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Chronicle

Quick start

What you were doing

On screen now

Permissions and tools

How it works

Connect an agent

Local clients

Packaged installs

Hosted agents and APIs

Files

MCP tools

App, API, and CLI

Configuration

Models

Privacy