Skip to main content
Glama
MerakOsiris

MemoryGuard

by MerakOsiris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MemoryGuard

No user-submitted related servers found.

    Related Servers

    • memory-ai-local

      Hsoley1
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that manages developer memory for coding agents, enabling shared project context, permissions, and audit trails across different agents.
      1
      -

    • Continuum MCP Server

      pouyahasanamreji
      F
      license
      Not graded
      quality
      D
      maintenance
      Shared memory and orchestration for coding agents, enabling persistent knowledge, multi-agent coordination, and a canonical workflow across MCP-compatible AI clients.
      59 npm
      110
      -

    • GroundMemory

      huss-mo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.
      3
      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.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct role, and descriptions actively prevent misselection (e.g., memory_read vs memory_search, audit vs explain, capabilities vs invoke). The lifecycle operations also explicitly state what they should not be used for.

    Naming Consistency4/5

    All tools share the memoryguard_ prefix and use readable snake_case, with memory operations following a consistent memory_<action> pattern. However, audit, explain, capabilities, invoke, and context_bootstrap deviate from a uniform verb_noun convention, creating minor inconsistency.

    Tool Count5/5

    Eleven tools is well-scoped for a governed-memory server: CRUD/search/status, audit/explain, context bootstrap, and a capability-discovery/invocation pair. Each tool has a meaningful place and the count feels neither bloated nor thin.

    Completeness4/5

    The surface covers memory creation, reading, searching, updating, soft-deletion, status inspection, audit, explanation, and task context bootstrapping. Minor gaps remain around explicit lifecycle transitions (e.g., restore/archive) and applying audit repairs, though the generic invoke tool provides a partial extension path.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources