Skip to main content
Glama
adeeljames

Claude Memory MCP

by adeeljames
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Claude Memory MCP

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.
      13 npm
      1
      MIT

    • memory-mcp

      chenxiaofie
      A
      license
      B
      quality
      B
      maintenance
      A persistent memory MCP server for Claude Code that automatically saves conversations and retrieves relevant history across sessions to provide context.
      17
      87 PyPI
      11
      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.
      -

    • recall

      Zavelinski
      A
      license
      A
      quality
      D
      maintenance
      A zero-dependency MCP server for cross-session memory recall in Claude Code. Provides lexical search, listing, and retrieval of past session memories to avoid re-explaining context.
      3
      6 npm
      MIT

    • mcp-assist-memory

      aliomraniH
      F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides a shared memory layer for Claude across claude.ai, Claude Code CLI, and Desktop, storing revisioned memory entries, session timelines, handoffs, and uploaded artifacts in SQLite.
      -

    • graphify

      Ibrohim-Bxone
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that stores decisions and summaries locally, enabling Claude to recall past context across chats.
      1
      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

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: clearing all memory, retrieving context, and saving a turn. No ambiguity.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern with underscores: clear_memory, get_context, save_turn. Fully consistent.

    Tool Count4/5

    With 3 tools, the set is minimal but appropriate for a focused memory management server, covering essential operations. Slightly thin but not problematic.

    Completeness3/5

    Covers basic lifecycle: create (save_turn), read (get_context), delete all (clear_memory). Missing update or selective delete functionality, which may be needed for finer control.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources