Skip to main content
Glama
claude-history-mcp

claude-history-mcp

by fifeek0

Related Servers

Alternatives to claude-history-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      our ChatGPT and Claude chat history in one local SQLite file, imported from their data exports. Read-only tools to search and read past conversations; no network.
      2
      5
      730 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Persistent memory + FTS5 full-text search for Claude Code conversation history. Indexes ~/.claude/projects/ JSONL into SQLite, exposes 10 MCP tools (store/recall/search memories, browse sessions, get summaries) plus prompts. Includes a web UI for visual exploration
      10
      88 npm
      97
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables comprehensive search and analysis of Claude Code conversation history using full-text search, optional semantic vector search, and conversation management tools. Provides fast SQLite-based indexing with role-based filtering, project organization, and hybrid search capabilities combining keyword and semantic matching.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables users to search locally across imported Claude, ChatGPT, and Claude Code conversations and retrieve surrounding turns with citations, while keeping indexing and storage on their own computer.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to search through its own past sessions using full-text search and resume them. Works offline with zero runtime dependencies.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to full-text search, list, and read your exported ChatGPT and Claude conversations from a local conversations.json file, running locally with read-only file access and no network requests. Supports both official export formats with automatic detection.
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: listing topics, browsing conversations, summarizing a conversation, searching messages, and fetching full messages. The uuid-based summary and full-message tools are clearly differentiated by scope.

    Naming Consistency4/5

    Mostly snake_case with verb_noun pattern (browse_conversations, search_history, get_conversation_messages), but conversation_summary is a noun phrase and list_all_topics inserts 'all', creating minor inconsistency.

    Tool Count5/5

    Five tools is a well-scoped, focused set for a read-only conversation history server; no tool feels redundant and the count matches the domain.

    Completeness4/5

    Core read operations (topics, browse, summary, search, full messages) are covered, but browse_conversations lacks pagination offset and a date filter despite the description, leaving minor gaps.