Skip to main content
Glama
mnemoverse

Mnemoverse Memory

by mnemoverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Mnemoverse Memory

No user-submitted related servers found.

    Related Servers

    • Kronvex

      Daftgoldens
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory API for AI agents — store, recall, and inject semantically-searchable context across sessions. EU-hosted, GDPR-compliant. Supports Claude, Cursor, Cline, and any MCP-compatible client.
      4
      2
      MIT

    • umo-memory

      UmoLab
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory for AI coding agents that stores and recalls preferences, decisions, and conventions via semantic similarity, with zero cloud dependencies and plug-and-play MCP integration for Claude Code.
      Apache 2.0

    • memmd-mcp

      matamong
      A
      license
      B
      quality
      D
      maintenance
      A shared memory layer for AI agents — one memory.md synced across Claude Desktop, Cursor, Claude Code, OpenAI Codex, and any MCP client.
      4
      2
      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.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: write/read/list/feedback/stats cover personal memory, create/invite/join/list cover shared rooms, and vault_list is clearly separate. Even the two list-style tools are sharply differentiated by search vs recency and personal memory vs rooms.

    Naming Consistency4/5

    Nine of ten tools follow the memory_<action> pattern, which is consistent and predictable. vault_list breaks both the prefix and word order, making it the one clear outlier.

    Tool Count5/5

    Ten tools is well-scoped for the server's three functional areas: personal memory, shared rooms, and vault inspection. Each tool has a clear job and none are redundant.

    Completeness4/5

    The personal memory lifecycle is complete with write, read, list recent, feedback, and stats, and shared-room workflows are well covered. Missing room leave/delete or vault write operations are gaps, but they are outside the core memory flow and can be worked around.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources