Chronicle MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_historyC | Search and filter historical transcripts. Options for method: 'semantic', 'keyword', 'date_range', 'related'. |
| get_chat_logsC | Retrieve lists of files, metadata, summaries, or specific message ranges. Options for view_type: 'content', 'metadata', 'summary'. |
| sync_workspace_dataC | Ingest and normalize external conversations or live transcripts. Options for source_type: 'agent_transcripts', 'cursor_agent_transcripts', 'local_path', 'raw_content'. |
| compile_project_insightsC | Analyze historical logs to extract tasks, briefs, or indices. Options for insight_type: 'action_items', 'knowledge_index', 'compare_chats', 'project_brief'. |
| maintain_storageC | Perform storage maintenance, deduplication, configuration, and capabilities retrieval. Options for op_type: 'compress', 'deduplicate', 'configure', 'capabilities'. |
| manage_session_stateC | Manage session auto-saving, folder watching, merging, exporting, and deletion. Options for action: 'save', 'register_auto_save', 'trigger_auto_save', 'watch_folder', 'merge', 'export_markdown', 'delete'. |
| save_handoff_receiptC | Save a structured, continuation-biased handoff receipt conforming to the strict state-machine DAG model. |
| get_handoff_statusC | Retrieve the current workspace handoff status, including active chain of receipts, blocked status, and any next safe action. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_session | Get system instructions for auto-saving conversations in the local Chronicle archive. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct operation: insights, logs, handoff status, storage maintenance, session management, handoff receipts, search, and data ingestion. No overlapping purposes, making selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., compile_project_insights, get_chat_logs). No mixing of styles, ensuring predictability.
With 8 tools, the server is well-scoped for its domain of workspace and chronicle management. Each tool serves a clear function without excess or insufficiency.
The tool set covers all key workflows: data ingestion, retrieval, search, analysis, maintenance, session management, and handoff procedures. No obvious gaps for the intended purpose.