Skip to main content
Glama
smallpinksquare

Codex History Hub

by smallpinksquare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Codex History Hub

No user-submitted related servers found.

    Related Servers

    • chist

      hiropon164
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for unified full-text search across chat histories from Claude Code, Codex, Cursor CLI, and Antigravity CLI, using SQLite FTS5. Provides read-only tools to search sessions, list conversations, and retrieve session details.
      MIT

    • NexusMem

      yaminbkk
      A
      license
      A
      quality
      A
      maintenance
      Indexes git history, shell commands with exit codes, project docs, and opt-in assistant transcripts into a local SQLite database, then serves ranked, token-budgeted context back over MCP. Uniquely links a failed shell command to the commit that fixed it, so agents can recall what was already tried and what worked.
      6
      145 npm
      13
      MIT

    • vshulcz/deja-vu

      vshulcz
      A
      license
      A
      quality
      A
      maintenance
      Indexes the session histories Claude Code, Codex CLI and opencode already write into a local searchable memory. MCP recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.
      1
      525 npm
      897
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: recent context retrieval, cross-account search, thread reading, project summary retrieval, and project summary update. The overlap between recent context and project summary is intentional, and descriptions clarify the difference.

    Naming Consistency4/5

    All tools share the 'history_' prefix and mostly follow a verb_noun pattern (get_recent_context, get_thread, get_project_summary, update_project_summary). The exception is 'history_search' which lacks an explicit object, but the pattern remains clear.

    Tool Count5/5

    With five tools, the set is well-scoped for a history hub: retrieval, search, and update operations. Each tool serves a clear purpose without redundancy.

    Completeness4/5

    The surface covers core history workflows: recent context, search, thread retrieval, and project summary read/update. A minor gap is the lack of an explicit list projects tool, but search and recent context can compensate.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources