Skip to main content
Glama
donggyun112

mcp-super-memory

by donggyun112
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-super-memory

No user-submitted related servers found.

    Related Servers

    • keymem

      donggyun112
      A
      license
      A
      quality
      A
      maintenance
      Associative key-graph memory for LLM agents — recall facts by association (recall → read_key → read_memory) instead of vector similarity alone, with persistent cross-session memory and cross-lingual keys.
      14
      1,611 npm
      3
      MIT

    • agent-memory-mcp

      Yarmoluk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables persistent, graph-based memory for AI agents, allowing them to store, traverse, and recall relationships between facts, decisions, and context across sessions for efficient reasoning and reduced token usage.
      MIT

    • neural-memory

      nhadaututtheky
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to persist memories across sessions and recall them through graph-traversal spreading activation over interconnected neurons with explicit relationship types, supporting multi-hop reasoning fully offline without embedding API costs.
      10
      243
      MIT
    • Memsolus MCP Server by memsolus

      Memsolus MCP Serverofficial

      memsolus
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.
      14
      14 npm
      MIT

    • dejaview-mcp

      JakeC77
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.
      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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct role in the memory lifecycle: creation (remember, remember_batch), retrieval (recall, list_memories, get_conversation), update (correct), deletion (forget), exploration (related), and maintenance (cleanup_expired, memory_stats). The overlap between remember and remember_batch is clearly explained as single vs batch.

    Naming Consistency5/5

    Names are consistently lowercase snake_case with clear verbs (recall, remember, correct, forget) and noun-prefixed operations (get_conversation, list_memories, memory_stats). No mixed conventions like camelCase or inconsistent verb styles.

    Tool Count5/5

    Ten tools provide comprehensive coverage without redundancy. Each tool earns its place, covering CRUD, batch operations, exploration, and system maintenance.

    Completeness4/5

    The set covers the full memory lifecycle: save, search, list, update, delete, link exploration, batch save, and maintenance. A minor gap is the lack of a direct 'get memory by ID' tool, though recall and related can surface memory content.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources