Skip to main content
Glama
MSR806

Agent Memory MCP

by MSR806
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Agent Memory MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • mem-universe

      H1an1
      A
      license
      A
      quality
      D
      maintenance
      Self-hosted MCP memory server that gives a multi-agent fleet one shared, git-backed memory for search, read, and write.
      8
      1
      MIT

    • 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

    • leafmem

      xdragonjia
      F
      license
      A
      quality
      A
      maintenance
      MCP server for LeafMem, a layered memory engine that gives AI agents persistent, scoped memory with local retrieval and optional embedding rerank. It exposes tools for capturing turns, storing memories, and building recall context.
      4
      10 npm
      -

    • mechabrain

      bbarrosdavi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides agentic memory management for markdown vaults, enabling hybrid search, governed writing, and maintenance of episodic, semantic, procedural, and working memories for LLM agents.
      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.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: creating, deleting, listing metadata, reading multiple, reading single, and updating memories. No overlap.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., create_memory, list_memories). The plural/singular distinction for read_memories vs read_memory is appropriate.

    Tool Count5/5

    6 tools is a well-scoped set covering full CRUD plus list and batch read operations. Not too few or too many.

    Completeness5/5

    The set provides complete lifecycle management for memories: create, read (single and batch), update, delete, and list metadata. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources