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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/smallpinksquare/cli-history-hub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server