Skip to main content
Glama
Sign In
Mnemoverse Memory

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: semantic memory search, recency listing, stats overview, graph inspection, room creation/joining/inviting/listing, feedback, and vault listing are all separable. The potentially overlapping read-style tools are explicitly differentiated by their descriptions.

    Naming Consistency5/5

    The tool set follows a consistent snake_case convention, with nearly all tools using the memory_ prefix and clear verb/noun structure. vault_list is a minor subsystem-specific exception but remains readable and predictable.

    Tool Count5/5

    Eleven tools is well-scoped for a memory server with private memory, shared rooms, graph inspection, feedback, stats, and vault listing. Each tool earns its place without excessive surface area.

    Completeness4/5

    Core workflows are well covered: write, read/search, recent listing, feedback, room lifecycle basics, graph inspection, stats, and vault alias listing. Notable gaps remain around memory deletion/update and room membership management, though deletion is explicitly handled outside MCP.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled

    Resources