Skip to main content
Glama
LogicMem

LogicMem MCP Server

Official
by LogicMem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to LogicMem MCP Server

No user-submitted related servers found.

    Related Servers

    • codebase-memory

      yuga-hashimoto
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI coding agents through the Model Context Protocol, enabling them to store and retrieve project knowledge across sessions.
      26 npm
      MIT

    • @vemdev/mcp-server

      vem-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents durable project memory via the Model Context Protocol, allowing them to read tasks, record decisions, search context, and sync snapshots to the cloud.
      13 npm
      MIT

    • Memclaw

      caura-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Governed shared memory platform for AI agents and agent fleets. Provides persistent memory, cross-agent knowledge sharing, permissions, audit trails, and multi-tenant isolation through a Model Context Protocol (MCP) server.
      4 npm
      501
      Apache 2.0

    • MAPI

      cabo0m
      A
      license
      Not graded
      quality
      D
      maintenance
      An auditable memory, lifecycle, and governance server for AI agents, providing durable memories with provenance, lifecycle management, and guarded workflows through the Model Context Protocol.
      Apache 2.0
    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

    B3.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    All 12 tools have clearly distinct purposes, split into two coherent groups: memory operations (log, recall, stats, session, health, outcome, reflect) and A2A operations (register, heartbeat, list_agents, write_shared, sync). No overlapping functionality.

    Naming Consistency5/5

    Tool names follow a consistent pattern: `logicmem_<group>_<action>`. Memory tools use `memory_` and A2A tools use `a2a_`. Verbs are descriptive (log, recall, stats, etc.), making the pattern predictable.

    Tool Count5/5

    With 12 tools covering memory management and agent-to-agent communication, the count is well-scoped. Each tool serves a distinct function without redundancy, fitting the server's purpose.

    Completeness4/5

    The set covers core memory operations (store, recall, stats, session, outcome, reflect, health) and A2A operations (register, heartbeat, list, write shared, sync). Minor gaps exist, such as no explicit delete/update for memories, but the design suggests permanence.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources