Skip to main content
Glama
xChuCx

agent-memory

by xChuCx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to agent-memory

No user-submitted related servers found.

    Related Servers

    • RepoRecall

      esannkv
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.
      MIT

    • auxly-memory-cli

      Tzamun-Arabia-IT-Co
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      2
      MIT

    • Codex Memory

      zhangtian-123
      A
      license
      B
      quality
      D
      maintenance
      Local Markdown-backed memory tools for Codex and other MCP-capable agents. Exposes durable agent knowledge via CLI and MCP server.
      5
      MIT

    • Global Agent Memory

      ozankasikci
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides local-first, project-aware durable memory for coding agents, with a human-reviewed Markdown vault, MCP daemon, and dashboard for managing and retrieving shared knowledge.
      42 PyPI
      14
      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.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: fetching context, proposing updates, and reporting status. There is no overlap or ambiguity in their purposes.

    Naming Consistency4/5

    All tools share the consistent memory. namespace and use an action-oriented style. fetch_context and propose_update follow verb_noun, while status is a noun-only deviation, but the pattern remains predictable.

    Tool Count5/5

    Three tools is well-scoped for a focused memory-management server. Each tool covers a necessary capability without bloat or redundancy.

    Completeness4/5

    The set covers the core memory lifecycle: read, write, and health/status inspection. A minor gap is that staged proposals cannot be approved or rejected directly through MCP tools, relying on external CLI commands instead.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources