Skip to main content
Glama
Sign In
memory-mcp

memory-mcp

by analyticsrequired
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memory-mcp

No user-submitted related servers found.

    Related Servers

    • dejaview-mcp

      JakeC77
      A
      license
      Not graded
      quality
      D
      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

    • 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
    • supermem

      supermemofficial

      LaxRaj
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables storing and querying a personal knowledge graph as a shared memory, allowing agents and tools to remember facts, entities, relations, and recall relevant context via natural language hybrid search.
      1
      MIT

    • local-memory-mcp

      mason-yb-zhang
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.
      -
    • Memsolus MCP Server

      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
      17 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

    A3.9/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: entities, relations, observations, and namespaces are cleanly separated. The read tools (read_graph, search_nodes, open_nodes) overlap conceptually but their descriptions explicitly state when to use each, eliminating misselection risk.

    Naming Consistency5/5

    All 13 tools follow a consistent verb_noun pattern (create_entities, add_observations, delete_relations, list_namespaces, rename_namespace, read_graph, open_nodes). No mixed conventions or vague verbs anywhere.

    Tool Count5/5

    13 tools is well within the ideal range and every tool earns its place: entity/relation/observation lifecycle plus a coherent four-tool namespace management set. No redundant or filler tools.

    Completeness4/5

    Strong coverage: create/delete for entities, relations, observations, plus full namespace CRUD (create, list, rename, delete) and three read modes. Minor gaps exist—no way to update an entity's type or name, and no relation update (only delete+recreate).

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources