Skip to main content
Glama
adamkwhite

Claude Conversation Memory System

by adamkwhite
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Claude Conversation Memory System

No user-submitted related servers found.

    Related Servers

    • MCP Memory Server

      PlumyCat
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude persistent memory by storing conversation context, entities, and enabling semantic search across sessions.
      21 npm
      1
      MIT

    • Claude Memory MCP

      adeeljames
      F
      license
      A
      quality
      D
      maintenance
      A lightweight MCP server that provides Claude Desktop with persistent memory across conversations by storing, summarizing, and retrieving conversation history.
      3
      -

    • ClaudeHistoryMCP

      jhammant
      A
      license
      A
      quality
      D
      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
      3 npm
      66
      MIT

    • RLM Knowledge Base

      cgaeking
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables Claude Desktop to search and read local documents via full-text and fuzzy search, providing direct access to indexed files without chunking.
      MIT

    • Memory-Man

      HelyeFab
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides persistent long-term memory for Claude Code, enabling storage, search, and retrieval of project knowledge across sessions.
      -

    • engram-mcp

      lowbridgee
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables semantic and keyword search over Claude Code conversation history stored locally, using hybrid search, local embeddings, and time-decay scoring.
      10 npm
      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

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources or actions: add/get/update are clear CRUD operations, and the metadata-specific searches (by_tag, by_session_id, by_conversation_type) are well-scoped. However, search_conversations and search_by_topic overlap conceptually, and the distinction between generic content search and topic search is not sharply defined.

    Naming Consistency4/5

    The naming is predominantly verb_noun snake_case, with add_conversation, get_conversation, update_conversation, and generate_weekly_summary following a clear pattern. The search tools are slightly inconsistent because some use search_conversations while others use search_by_tag/search_by_session_id/search_by_conversation_type, but the style is still recognizable and predictable.

    Tool Count4/5

    Ten tools is a reasonable size for a conversation memory system, and the CRUD core plus search variants cover most expected workflows. The count is slightly search-heavy, with six retrieval-related tools, but none feel redundant enough to remove outright.

    Completeness3/5

    The system covers add, get, update, search, summary, and stats, which handles the core lifecycle for stored conversations. Notable gaps include no delete/forget operation, no list-all conversations tool, and no dedicated search_by_user_id even though user_id is described as a universal metadata field.

    Maintenance

    ActivitySlowing
    ResponsivenessResponsive

    Resources