Skip to main content
Glama
jryom

agentsmd-memory

by jryom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to agentsmd-memory

No user-submitted related servers found.

    Related Servers

    • mcp-memory-vault

      AleBrito124356
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives agents persistent memory with namespaced facts, tags, full-text search, and TTL expiry, all running locally on SQLite with zero external dependencies.
      3
      MIT

    • Continuum

      mittalpk
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing agents with persistent working, episodic, and semantic memory backed by CockroachDB, exposed via tools to store, recall, list, and forget memories.
      MIT
    • yantrikdb-mcp by yantrikos

      yantrikdb-mcpofficial

      yantrikos
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing cognitive memory tools (remember, recall, think, etc.) for AI agents, enabling forgetting, consolidation, and contradiction detection.
      174
      Apache 2.0

    • Agent Memory

      Masikomoore
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
      3
      -

    • saor-mcp

      ubajxn
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.
      9
      17 npm
      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.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one saves new facts, the other removes outdated ones. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent 'memory_' prefix followed by a verb ('save', 'forget') that accurately describes their action.

    Tool Count4/5

    With only 2 tools, the server is minimal but well-scoped for its purpose of managing a single memory file. It could benefit from a read or update tool, but the count is not inappropriate.

    Completeness3/5

    The set covers the core operations of adding and removing facts, but lacks the ability to explicitly list or update facts. However, agents can use their own read tools to inspect the file, and updates can be simulated by a forget-then-save sequence.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources