Skip to main content
Glama
liyexiaoyi

mnemosis-mcp

by liyexiaoyi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mnemosis-mcp

No user-submitted related servers found.

    Related Servers

    • Cortex

      ryanfrigo
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.
      3 npm
      MIT

    • mnemosyne-mcp

      CodeCoreLab
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with persistent local memory management, including semantic recall, knowledge graph traversal, and automatic memory consolidation, enabling structured long-term memory across MCP clients.
      Apache 2.0

    • memento-mcp-server

      jee1
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, human-like memory infrastructure via MCP, enabling them to store, search, summarize, and forget episodic, semantic, procedural, and working memories across sessions.
      293 npm
      MIT

    • aimemory

      George3307
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents persistent memory with semantic search, automatic extraction, and memory decay, accessible via MCP protocol.
      7 npm
      MIT
    • Hicortex - AI Fleet Memory by gamaze-labs

      Hicortex - AI Fleet Memoryofficial

      gamaze-labs
      F
      license
      A
      quality
      B
      maintenance
      Shared fleet memory for AI agents — what one agent learns, the whole fleet knows. Nightly self-correction: stale facts rewritten in place, duplicates merged. Recall pushed into every prompt in supported coding agents. Self-hosted.
      8
      11
      2
      -
    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

    C2.7/5.0

    Scored across 98 tools

    Disambiguation2/5

    With 98 tools, many share overlapping responsibilities (e.g., practice_report/practice_session/practice_due/practice_answer; memory_status/memory_audit/memory_health/memory_map/stats; sleep/sleep_replay/sleep_and_plan; plan/replan/plan_rewrite/plan_quality/plan_tracker). An agent selecting a tool will frequently need to parse subtle description differences, and several report tools seem to summarize the same underlying state.

    Naming Consistency4/5

    Tool names mostly use snake_case and many follow verb_noun, but there are many noun-phrase names (memory_health, schema_report, lifecycle_audit, dependency_map, concept_cover) and one-word commands (sleep, check, update, plan, search). This is a readable convention but not consistently predictable.

    Tool Count1/5

    98 tools is extreme for any MCP server. Even if each tool has a cognitive justification, this scale makes the tool set hard to navigate and causes selection latency, so it is not well-scoped.

    Completeness5/5

    The surface covers the full memory lifecycle—store, retrieve, update, forget, restore, batch review, spaced repetition, sleep consolidation, intentions, planning, reasoning, exports, and audits. There are no obvious dead ends; every major operation appears to have at least one tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources