Chronicle MCP

Name: Chronicle MCP
Author: Leviathan0x0

by Leviathan0x0version 1.6.2i★ –iRuns on your computer

Registry nameio.github.Leviathan0x0/chronicle-mcp

Install

Overview

Description from the maker (original English)

Local, private AI chat history search & memory: BM25 over your Cursor, Claude and ChatGPT chats.

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_BASE_DIR, TRANSCRIPTS_DIR

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-mcp-server"
      ],
      "env": {
        "CHRONICLE_BASE_DIR": "your-value",
        "TRANSCRIPTS_DIR": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add chronicle --env CHRONICLE_BASE_DIR=your-value --env TRANSCRIPTS_DIR=your-value -- uvx chronicle-mcp-server

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-mcp-server"
      ],
      "env": {
        "CHRONICLE_BASE_DIR": "your-value",
        "TRANSCRIPTS_DIR": "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-mcp-server"
      ],
      "env": {
        "CHRONICLE_BASE_DIR": "your-value",
        "TRANSCRIPTS_DIR": "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_BASE_DIR env
Folder for the chat archive and search index. Defaults to ~/.chronicle (or the folder saved with chronicle --chats-folder).
TRANSCRIPTS_DIR env
Override folder scanned by sync_workspace_data(source_type='agent_transcripts'). Defaults to each editor's own transcript folder.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Leviathan0x0, 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 5662 servers in this category
Published to the registry more recently than 74% of the other 5662 servers in this category
Basic checks equal to or better than 100% of the other 5662 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 MCP 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 (1.6.2) reached the registry 13 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 MCP: Local AI Chat History Search & Memory

Private, offline memory for your AI coding agents. Chronicle MCP (chronicle-mcp-server) is a local stdio MCP server that indexes your Cursor, Claude, ChatGPT and Cline chat transcripts on your own machine and serves BM25 search over them, so agents can recall past conversations without re-pasting them, using up to 40% fewer context tokens. Your archive and index stay on disk: no cloud service, account, or API key.

Why · CLI Mechanics · Setup Wizard · Tool Catalog · Installation · Auto-Save · Tests · Comparison · FAQ · License

Chronicle is a Model Context Protocol (MCP) server that syncs, cleans, formats, and indexes AI chat transcripts entirely on your machine. By bridging the gap between local editor history and large language model contexts, Chronicle allows agents to search, compare, retrieve, and reference past conversation logs. It features optimized token-saving heuristics that compress code blocks and limit message lengths, reducing context window utilization by up to 40 percent.

Listed on

What's new in 1.6.2

Fixes fresh installs. Earlier releases let pip install mcp 2.x, which the server cannot run on. The dependency is now mcp>=1.22,<2.
Rewritten tool definitions. Every tool has a title, a description of what it does and when to use it, side effects and return value, and annotations (readOnlyHint, destructiveHint, ...). Every parameter is documented and every operation selector is an enum.
Real error results. Failures now come back with isError: true, and unknown operation names are rejected instead of silently running a different operation.
New ways to run it: uvx chronicle-mcp-server, chronicle serve, chronicle --version and a Dockerfile.
Server instructions, a `recall_past_work` prompt, and two resources: chronicle://capabilities and chronicle://chats.

What's new in 1.6.1

CI on Python 3.10 to 3.13, plus build and twine check on every push and pull request.
Accurate tool catalog: 8 tools plus the start_session prompt, which maintain_storage(op_type="capabilities") now reports too.
Richer PyPI metadata (project links, keywords, classifiers) and a cleaner repository with no committed build artifacts.

See the full CHANGELOG for earlier releases.

Key Architectural Capabilities

Format Normalization Engine

AI providers and editor clients save conversation logs in diverse formats. Chronicle normalizes these structures into a standard role-and-content message format:

ChatGPT Exports: ChatGPT exports conversation histories in recursive mapping node structures. Chronicle traverses and flattens these maps, sorts messages chronologically by creation timestamp, and extracts the plain-text message threads.
Claude Exports: Claude structures messages as flat lists nested under the chat_messages field. Chronicle parses these lists, maps custom sender roles (such as human and assistant) to standard roles, and cleans the text strings.
Generic and Markdown Formats: Chronicle includes parsers for flat JSON message lists (such as Cline or Continue) and structured Markdown logs (mapping headers like User and Assistant to message boundaries).

Context Token Optimization

Large chat logs can quickly exhaust context windows and increase API costs. Chronicle implements proactive token-saving mechanisms:

Code Block Summarization: Automatically replaces verbose code blocks with metadata summaries indicating the programming language and line count. This behavior can be disabled on demand to read full code snippets.
Length Limiting: Truncates extremely long individual messages at a configurable character threshold, appending a notice that the user can re-run the tool with expanded limits if necessary.

Context Window Token Savings Graph

To verify these savings, we executed multi-turn conversation benchmarks. The graph below displays total token usage over a sequence of message turns:

By condensing repetitive syntax and large raw code snippets, Chronicle achieves up to 40 percent token savings, directly lowering API usage costs and preventing context-window exhaustion.

Hybrid Splitting & BM25 Scoring Search Engine

To make workspace searches extremely sharp and retrieve context-aware answers, Chronicle incorporates a state-of-the-art retrieval pipeline:

Hybrid Document Splitting: Slices long conversations into logical parts at indexing time. Splits are triggered temporally if a gap of more than 1800 seconds (30 minutes) occurs between consecutive messages, or lexically if the Jaccard similarity of vocabulary sliding groups of 4 messages drops below 0.12. Each split is stored and queried as a virtual document (filename__chunk_idx).
Okapi BM25 Scorer: Replaces naive keyword matching and raw TF-IDF with Okapi BM25 scoring (k1 = 1.5 and b = 0.85). The parameter b = 0.85 enforces an aggressive length penalty, which ensures long, rambling chat logs do not overshadow short, precise bug fixes.
Handoff Receipts Prioritization: Integrates a direct tool to save compact agent state files documenting modified paths, commitments, skipped tests, and next actions. Active handoff receipts are automatically prioritized and bubbled to the very top of search results.

Command Line Interface Mechanics

The cli.py file serves as the system's entry point, registering a unified chronicle command on the system path via the pyproject.toml configuration (chronicle = "cli:main").

1. Interactive Setup Wizard

Chronicle features an interactive, zero-dependency TTY setup wizard. Running chronicle setup or executing chronicle without arguments in an interactive terminal starts the setup flow:

[!TIP]

The setup wizard is styled with a premium purple theme, supporting arrow-key navigation, spacebar toggles, inline input editing, and real-time path validation!

Keyboard Navigation & Controls

Use the following controls when interacting with the select menu:

Command / Action	Key Control	Description
Move Highlight	`▲` Up / `▼` Down Arrow Keys	Navigates the interactive list focus
Toggle Checkbox	`Spacebar`	Selects or deselects the highlighted app
Enter Custom IDE	Navigate to Other & type	Type custom app directory directly inline
Erase Character	`Backspace`	Removes characters inside the custom entry
Confirm & Inject	`Enter`	Validates target existence and runs config injection
Cancel Setup	`Ctrl + C` or `Escape`	Aborts setup process cleanly

Wizard Phases & Actions

The wizard guides you through the following phases:

Step	Phase Name	What You Do	Result & Behavior
Step 1	Monolithic Split Engine	Input JSON file path (or press `Enter` to skip)	Automatically partitions unified chat history exports
Step 2	Storage Directory Configuration	Specify directory path (or press `Enter` for default)	Creates local storage folder for transcripts
Step 3	Interactive IDE Selection	Toggle checkboxes, navigate submenus, type custom targets	Performs TTY selection and checks path validation
Step 4	Config Injection & Live Dashboard	Review final summary configuration	Injects server configs into target IDE settings

[!IMPORTANT]

HOW TO USE THE WIZARD — A STEP-BY-STEP SHOWCASE GUIDE

1. Start the Process: Launch the wizard with chronicle setup in your terminal.

2. Split Monolithic Files: Paste the path to your exported conversations.json (from ChatGPT or Claude). This splits them into clean individual threads inside your chats folder.

3. Define Your Chats Directory: Keep the default ~/universal-chats folder or type a custom path.

4. Select Your Target IDEs:

* Press Down Arrow to scroll down to VS Code, Trae, etc.

* Press Space to toggle selections.

* If you select Antigravity, checking it will automatically expand sub-choices (Antigravity IDE, Antigravity 2.0, Antigravity CLI) right underneath!

* Scroll down to Other (Enter custom entry) and type any system-specific folder name to add emerging editors.

* Real-time Path Validation: If the custom configuration path parent doesn't exist, a warning alerts you at the bottom: ⚠ App/IDE " " was not found on your system.. Erase it with Backspace or type a valid path to proceed.

5. Complete and Launch: Press Enter to write the JSON configuration file for all selected apps. The Live Environment Dashboard will display a complete summary of your workspace configs.

Click to expand step-by-step Setup Walkthrough

Step 1: Launch the Setup Wizard

Run the setup command:

chronicle setup

Step 2: The Monolithic Split Engine

The wizard asks if you want to partition any monolithic chat logs (such as the single conversations.json from ChatGPT/Claude exports) into separate files in your new storage folder:

── Chronicle Archive Setup ─────────────────────────────────────

Do you want to split a single conversations.json file? Enter path to export file (or press ENTER to skip):

Step 3: Configure Storage Path

Define the folder path where Chronicle will clean and store all conversation history:

Enter path to folder containing your conversations [Default: ~/universal-chats]:

✓ Using existing storage directory: /Users/username/universal-chats Successfully set chats directory to: /Users/username/universal-chats

Step 4: Interactive IDE Selector

An interactive selection menu with a premium purple theme. Navigate with the arrow keys, toggle checkboxes with the Spacebar, edit custom inputs

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

Chronicle MCP

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 MCP: Local AI Chat History Search & Memory

Listed on

What's new in 1.6.2

What's new in 1.6.1

Key Architectural Capabilities

Format Normalization Engine

Context Token Optimization

Context Window Token Savings Graph

Hybrid Splitting & BM25 Scoring Search Engine

Command Line Interface Mechanics

1. Interactive Setup Wizard

Step 1: Launch the Setup Wizard

Step 2: The Monolithic Split Engine

Step 3: Configure Storage Path

Step 4: Interactive IDE Selector