Chronolog
Record and retrieve agent interactions in a ChronoLog log store.
claude mcp add --scope project clio-chronolog -- clio-kit mcp-server chronolog
Install the launcher first. Restart your client after setup. Configuration locations →
Check the connection
clio-kit doctor --server chronolog --connect
Checks prerequisites and tool discovery. Test on known input to verify results. Native backends may require additional setup.
Tools
start_chronologConnect to ChronoLog, create a chronicle, and acquire a story handle.
record_interactionLog a user message and LLM response to the active ChronoLog story.
stop_chronologRelease the story handle and disconnect from ChronoLog.
retrieve_interactionRetrieve logged records from a chronicle and story, with optional time filtering.
Details
Writes the records to a new text file in the server's working directory and returns that file's absolute path, or "No records found.".
Examples
Replace example paths with your own files and check the returned results.
1. Session Logging and Analysis
Start logging our conversation, then after we discuss machine learning concepts, retrieve the interaction history for analysis.
Tools called:
start_chronolog- Initialize logging sessionrecord_interaction- Log conversation eventsretrieve_interaction- Generate interaction history
This prompt will:
- Use
start_chronologto create a new chronicle and story - Automatically log interactions using
record_interaction - Extract conversation history using
retrieve_interaction - Provide structured session analysis
2. Multi-Session Context Sharing
Connect to the research chronicle and retrieve yesterday's discussion about neural networks to continue our conversation.
Tools called:
start_chronolog- Connect to existing chronicleretrieve_interaction- Fetch historical interactions
This prompt will:
- Connect to existing research chronicle using
start_chronolog - Retrieve previous session data using
retrieve_interaction - Enable context continuation across sessions
- Support multi-client collaborative workflows
3. Structured Event Documentation
Begin recording our software design discussion, ensuring all architectural decisions and code examples are captured for future reference.
Tools called:
start_chronolog- Begin structured loggingrecord_interaction- Capture design decisionsstop_chronolog- Complete session
This prompt will:
- Initialize structured event logging using
start_chronolog - Capture all conversation elements using
record_interaction - Maintain detailed architectural documentation
- Provide clean session termination using
stop_chronolog
Native backend configuration
Build the archive reader against your native ChronoLog checkout and set HDF5_READER_BIN, CHRONO_CONF, PYTHONPATH, and LD_LIBRARY_PATH. Select UV_PYTHON matching the native client ABI. Retrieval preserves quotes/newlines; allow the configured archive flush interval after recording. See the native reader build instructions.