cli-history-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HISTORY_HUB_DB | No | Path to the SQLite database used by the Hub. Overrides the default runtime location (e.g., %LOCALAPPDATA%\CLIHistoryHub on Windows, XDG data on Linux, ~/Library/Application Support/CLIHistoryHub on macOS). Equivalent to the --db command-line argument. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| history_get_recent_contextB | Get a project overview plus recent primary conversation summaries across registered agents. Subagents are excluded by default. |
| history_searchA | Search older cross-project history across every registered agent. Call only when the user explicitly asks to search past history, names an older date/source/topic, or recent context is insufficient. |
| history_get_threadB | Read a selected history thread after identifying it via recent context or search. Full mode should be used only when the user explicitly requests the full thread. |
| history_list_connectorsA | List registered history connectors, their capabilities, and indexed source/thread counts. |
| history_get_project_summaryA | Get the durable overview of a project without loading conversation transcripts. |
| history_update_project_summaryA | Update the confirmed durable project overview in the independent Hub only. Never writes to any source CLI session files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes, but history_get_recent_context and history_get_project_summary both return project overviews, which could cause confusion. The other tools (search, get_thread, list_connectors, update_summary) are unambiguous.
All tools use the history_ prefix with snake_case and mostly follow a verb_noun pattern (get_recent_context, get_thread, list_connectors, get_project_summary, update_project_summary). The exception is history_search, which uses a bare verb, but the overall style is consistent.
With six tools, the set is well-scoped for managing CLI history—covering retrieval, search, thread access, connector listing, and project summary management. This is an appropriate size, not too thin or overwhelming.
The tools cover the core workflows: recent context, historical search, thread retrieval, connector discovery, and project summary viewing/updating. No critical operations are missing for the stated purpose of a history hub.