Skip to main content
Glama
Vvkmnn

Claude Historian

by Vvkmnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Claude Historian

No user-submitted related servers found.

    Related Servers

    • Cairn

      veax-project
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that backs up and syncs Claude Code conversations across accounts, and lets Claude search your complete history via natural language.
      GPL 3.0

    • ClaudeHistoryMCP

      jhammant
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that makes Claude Code conversation history searchable and proactively useful by indexing past sessions with hybrid BM25+TF-IDF search, extracting decisions and solutions, and auto-injecting relevant project context at session start.
      9
      7 npm
      66
      MIT

    • memex

      dioniipereyraa
      A
      license
      A
      quality
      D
      maintenance
      MCP server that indexes Claude.ai chats and local Claude Code sessions, enabling semantic and keyword search across all your conversations with Claude.
      6
      33 PyPI
      5
      MIT

    • smart-fork

      recursive-vibe
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for Claude Code that enables semantic search of past session transcripts and intelligent session forking, allowing users to find and resume from relevant previous conversations with full context.
      13
      8
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, such as extract_compact_summary for session summaries and find_file_context for file-related conversations. However, find_similar_queries and search_conversations could potentially overlap in functionality, as both involve searching through conversation history, which might cause minor confusion for an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as extract_compact_summary, find_file_context, and search_conversations. This predictability makes it easy for an agent to understand and navigate the tool set without naming-related confusion.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose of analyzing conversation history and patterns. Each tool appears to serve a specific function, such as summarizing sessions, finding errors, or searching plans, making the count appropriate and manageable for the domain.

    Completeness4/5

    The tool set covers key aspects of conversation analysis, including summarization, searching, error resolution, and pattern detection. A minor gap might be the lack of tools for modifying or annotating historical data, but the surface is largely complete for querying and insights, allowing agents to work effectively within the domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources