Chron MCP
- nivaya/chron
Chron is a MCP server that stores timestamped AI conversation audit logs locally in SQLite.
About
Chron is an MCP server that records every AI conversation as a timestamped audit log in a SQLite database you control locally. Developers who rely on agents for customer support, code changes, or sensitive research often lack a durable history when sessions end or tools rotate; Chron gives you a searchable, owned artifact instead of scattered chat exports. Configure CHRON_DB_PATH to place the database on disk you trust, wire chron-mcp over stdio in Claude Code or Cursor, and use the log when debugging bad outputs, proving what was agreed in a client thread, or improving prompts over time. It is lightweight operations tooling—not a full APM stack—aimed at people who want accountability without shipping conversation data to a third-party analytics product.
- Writes timestamped audit records for AI conversations into local SQLite
- You own the database file—no vendor cloud log lock-in
- CHRON_DB_PATH configures where the SQLite store lives
- npm chron-mcp 0.1.7 with stdio MCP transport
- Fits privacy-conscious solo builders who need a paper trail of agent sessions
Chron MCP by the numbers
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add --env CHRON_DB_PATH=YOUR_CHRON_DB_PATH chron-mcp -- npx -y chron-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | chron-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Repository | nivaya/chron ↗ |
What it does
Keep a local, timestamped audit trail of AI conversations in SQLite so you can review what the agent said and did without sending logs to the cloud.
Who is it for?
Privacy-minded developers who want a local conversation paper trail for support, compliance, or post-incident review.
Skip if: Skip if you need centralized multi-user analytics, real-time dashboards, or cloud-hosted log search at scale.
What you get
After you register Chron, each conversation can be persisted to your SQLite file so you can audit and revisit agent activity on your own terms.
- Persistent timestamped conversation audit records in SQLite
- Configurable local database location via CHRON_DB_PATH
- Stdio MCP integration for ongoing session logging
By the numbers
- Server version 0.1.7 as npm identifier chron-mcp
- stdio MCP transport
- One documented env var: CHRON_DB_PATH
Recommended MCP Servers
Agent Audit MCPImmutable audit trail for agent-to-agent interactions2
Agentguard47 MCPRead-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.4
Agentic Observability MCPAgent tracing, cost tracking, anomaly detection for LLM agents
Agent Incident Relay MCPAgent Incident Relay MCP — Article 73 5-clock broadcaster.
Agent Infra MCP18 tools: agent memory, API drift detection, and HMAC-signed trust receipts
Agentmonitorrelay MCPAI agent run monitoring with incident replay and SLA receipts.How it compares
Local conversation audit MCP, not a full observability platform or error-tracking service.
FAQ
Who is Chron MCP for?
Developers and operators who run AI agents daily and want an owned, timestamped history of what was discussed without cloud logging.
When should I use Chron MCP?
Use it once you depend on agents for production-adjacent work and need to monitor, review, or audit past conversations from your machine.
How do I add Chron MCP to my agent?
Register the chron-mcp npm package as a stdio MCP server in your agent config and set CHRON_DB_PATH to your preferred SQLite file path.