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.
      34 npm
      110
      -

    • GroundMemory

      huss-mo
      A
      license
      Not graded
      quality
      A
      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
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with explicit boundaries: read vs search vs write vs update vs delete vs status vs audit vs explain vs bootstrap vs capabilities vs invoke. The descriptions include 'Do not use' clauses that further reduce ambiguity.

    Naming Consistency5/5

    All tool names follow the consistent pattern memoryguard_<resource>_<verb> or memoryguard_<verb> where appropriate (e.g., memoryguard_memory_search, memoryguard_memory_read). No mixing of conventions.

    Tool Count5/5

    11 tools is well-scoped for a memory management server with governance features. Each tool appears to earn its place by covering distinct aspects of memory lifecycle and system introspection.

    Completeness5/5

    Full CRUD coverage for memories (write, read, update, delete) plus search, status, audit, explain, bootstrap, capabilities, and invoke. The surface includes both data operations and system-level discovery/control, leaving no obvious gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources