Skip to main content
Glama
palimpsest-labs

Unified History MCP

by palimpsest-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Unified History MCP

No user-submitted related servers found.

    Related Servers

    • Unified History MCP

      jmars
      A
      license
      A
      quality
      B
      maintenance
      Config-driven MCP server for cross-domain full-text search across agent session logs, meeting transcripts, and notification files.
      7
      1
      MIT

    • transcript-search-v2

      jsundquist
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that indexes local Claude Code transcripts and provides keyword, phrase, semantic, and date-range search, plus full context/session recall.
      -

    • MCPedia

      asepharyana
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.
      15 npm
      MIT

    • elasticsearch-logs

      ws135y
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Elasticsearch log querying. Enables natural language search, filtering, context retrieval, and aggregation of logs.
      -
    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 7 tools

    Disambiguation4/5

    Most tools are clearly distinct: list_domain enumerates files, read retrieves entries, summary provides AI-generated overviews, and rebuild manages indexes. The three search-related tools (search, search_history, search_log) could cause some confusion, but their descriptions clearly separate domain search from specific-file searches.

    Naming Consistency3/5

    Naming conventions are mixed: some tools use single verbs (search, read, summary, rebuild) while others use verb_noun patterns (list_domain, search_history, search_log). 'summary' is a noun rather than an imperative verb, breaking the expected pattern. Overall, the names are readable but not uniformly styled.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose of providing unified search and read access to historical data. Each tool serves a distinct function without unnecessary bloat, and the count is appropriate for the domain.

    Completeness4/5

    The tool set covers the core lifecycle for a read-only history server: searching, listing, reading, and summarizing entries, plus index maintenance. The only notable gap is that the summary tool does not support the notifications domain, and there is no explicit tool for configuring domains (though rebuild handles index updates).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources