Skip to main content
Glama

Related Servers

Alternatives to memcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Persistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.
      1,117 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A remote MCP server that gives Claude (and ChatGPT/Gemini) persistent read/write access to your own memory: books, games, projects, notes, and freeform facts.
      -
    • 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
    • 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      A persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.
      32 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing persistent, searchable memory management for AI workflows, enabling Claude Code to store, retrieve, and organize context through CRUD operations and knowledge tools.
      MIT

    TDQS

    A3.8/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., memcp_remember vs memcp_load_context, memcp_recall vs memcp_search), but some overlap exists between recall and search, and between consolidate and retention. Overall, an agent can distinguish them with moderate effort.

    Naming Consistency5/5

    All tools follow a consistent memcp_ prefix with snake_case naming. Verbs are uniform (e.g., remember, recall, search, forget, consolidate) and the pattern is predictable, aiding agent comprehension.

    Tool Count4/5

    24 tools is slightly high but appropriate for a comprehensive memory server covering storing, retrieving, managing, consolidating, and cleaning up knowledge. Each tool earns its place, though some like memcp_ping are minimal.

    Completeness5/5

    The tool surface covers the full lifecycle: create (remember, load_context), read (recall, search, get_context, inspect_context, peek_chunk), update (reinforce, consolidate), delete (forget, clear_context), and maintenance (retention, restore, list, stats). No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues