Skip to main content
Glama

Related Servers

Alternatives to cli-history-hub

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides a read-only interface to audit and continue coding agent sessions by extracting plans, intents, and edit authorship from history across multiple agents (Claude, Codex, OpenCode, Antigravity, Pi) via MCP, CLI, and Python SDK.
      18
      29 PyPI
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to persistently store and retrieve conversation history with hybrid semantic and keyword search, cross-encoder reranking, session filtering, and archiving through MCP tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching and retrieving local chat history from Codex and Claude CLI sessions via BM25 full-text search and MCP tools.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A powerful tool for exploring, searching, and managing your shell command history through the MCP (Model Control Protocol) interface. This project allows you to easily access, search, and retrieve your previously executed shell commands.
      2
      MIT

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues