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
      A
      quality
      B
      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.
      8
      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.
      176
      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
      4 npm
      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.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    memory_save (add facts), memory_forget (fix/remove wrong facts), and memory_review (bulk cleanup on request) target largely distinct actions, and the descriptions explicitly distinguish the triggers. There is mild overlap between forget and review since both edit existing content, but the conditions (evidence-based correction vs. user-requested cleaning) keep them separable.

    Naming Consistency5/5

    All three tools follow an identical memory_<verb> pattern with clear, action-oriented verbs (save, forget, review). The convention is fully consistent and readable.

    Tool Count4/5

    Three tools is on the thin side but each maps to a distinct memory lifecycle action (add, correct, clean), so none feel redundant. It sits at the low end of the ideal range but is defensible for this narrow purpose.

    Completeness3/5

    Save, correct/forget, and prune are covered, but there is no explicit read/list/recall tool to surface stored memory, and none of the tools actually writes files (all return instructions for the agent's own editing tools). The lifecycle is mostly present but has a notable retrieval gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources