Skip to main content
Glama
zhadyz

Mnemosyne MCP

by zhadyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Mnemosyne MCP

No user-submitted related servers found.

    Related Servers

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

    • 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
      288 PyPI
      240
      MIT

    • 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

    • Memory Palace

      jeffpierce
      A
      license
      Not graded
      quality
      C
      maintenance
      Persistent semantic memory for AI agents, enabling storage, semantic search, knowledge graph connections, and inter-instance messaging across conversations using local models via Ollama.
      50
      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 17 tools

    Disambiguation4/5

    Most tools have clear distinct purposes, but search_nodes, semantic_search, and open_nodes all relate to finding nodes with subtle differences; similarly, read_graph, get_graph_at_time, and get_decayed_graph are distinct temporal/decay views but could be confused by an agent.

    Naming Consistency4/5

    The naming is largely consistent with verb_noun snake_case (e.g., create_entities, delete_relations, add_observations). Minor deviations include 'read_graph' vs 'get_graph_at_time' and 'search_nodes' vs 'semantic_search', which break the pattern slightly but remain readable.

    Tool Count4/5

    17 tools is slightly above the typical 3-15 sweet spot, but the knowledge graph domain with history, embeddings, and temporal views justifies the additional tools. It feels a bit heavy but not excessive.

    Completeness3/5

    The surface covers creation, deletion, and relation management well, but there are notable gaps: no update_entities or update_observations, and no explicit single-entity getter (open_nodes is name-based rather than ID-based). These gaps force agents to work around the incomplete CRUD lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources