Skip to main content
Glama
MarceloCaporale

codex-agent-mem

by MarceloCaporale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to codex-agent-mem

No user-submitted related servers found.

    Related Servers

    • whitemagic

      lbailey94
      A
      license
      B
      quality
      A
      maintenance
      Provides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.
      2
      1
      MIT

    • mcp-light-memory

      PeterPirog
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.
      MIT

    • nuzo-memory

      fabionfsc
      A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0

    • ITHZ MCP

      thegobi
      F
      license
      Not graded
      quality
      C
      maintenance
      Local-first deterministic project memory for AI coding agents, with context packs, decisions, gates, risks, scoped claims and explicit checkpoints in project-owned files.
      -

    • mcp-chest-memory

      siosig
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.
      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

    B3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some potential overlap between retrieval tools like mem_get, mem_search, mem_recent, and mem_recent_changes. Descriptions help differentiate them, but the distinctions may still cause confusion.

    Naming Consistency5/5

    All tools follow a consistent mem_verb_noun or mem_noun_verb pattern in snake_case, making them predictable and easy to parse. No mixed conventions are present.

    Tool Count3/5

    28 tools is on the high side, covering a broad set of memory-related operations. While each tool has a defined purpose, the count feels slightly heavy for a single server.

    Completeness3/5

    The tool set covers many memory management aspects, but lacks explicit update and delete operations for stored observations (only create via mem_note_create). This creates a notable gap in the typical CRUD lifecycle.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources