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 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: write, read, feedback, stats, room management (create/invite/join/list), graph inspection, recent listing, and vault listing. The only potential overlap—memory_read vs memory_list_recent—is explicitly resolved by their descriptions (semantic search vs chronological listing), and stats vs graph are differentiated as summary vs detailed edges.

    Naming Consistency4/5

    All tools use lowercase snake_case, and 10 of 11 share the memory_ prefix; vault_list is a minor deviation. The internal pattern mixes verbs (write, read, create_room) and nouns (feedback, stats, graph), but remains readable and predictable enough for consistent use.

    Tool Count5/5

    11 tools is well-scoped for a memory server with shared rooms, feedback, graph, and vault functionality. Each tool earns its place, and the count avoids both bloat and thinness.

    Completeness4/5

    The surface covers the full memory lifecycle (write, read, feedback, stats, graph, recent) and core room management (create, invite, join, list). Minor gaps exist: no way to leave or delete a room, and the vault supports only listing (likely by design), but these do not block typical agent workflows.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources