Skip to main content
Glama
agentage

@agentage/mcp-memory

Official
by agentage

Related Servers

Alternatives to @agentage/mcp-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves a unified local memory bank over a stdio MCP server, exposing five tools and one resource so any MCP-capable harness can list, search, and read memories imported from Claude Code, Codex, Cursor, Kimi Code, and ZCode. It gives agents a single read-only view of user preferences, feedback, project state, and reference material stored as plain Markdown files.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server exposing the dek-memory hybrid memory engine over stdio, with optional ChatGPT tools for managing account memories via a browser profile.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude Code to give LLM agents long-term memory by exposing remember, recall and forget tools over stdio, backed by a hybrid BM25 and vector store that reinforces frequently used memories.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients like OpenCode or Claude to use EbbingFlow long-term memory across sessions through stdio tools for writing, retrieving, and chatting with remembered context.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes repo-native, self-verifying memory to coding agents over stdio MCP, letting them recall ranked past decisions, record new claims with verifiable receipts, and check the health and stats of stored memory. Keeps agent context honest by surfacing memories whose evidence no longer holds.
      127 npm
      MIT

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a unique, well-defined purpose: create/overwrite (write), modify existing (edit), delete (delete), read by path (read), browse folder tree (list), and keyword search (search). No overlapping functionality.

    Naming Consistency5/5

    All tools follow the 'memory__<verb>' pattern with clear, single-word verbs (delete, edit, list, read, search, write). Consistent and predictable.

    Tool Count5/5

    Six tools cover the essential CRUD and browsing operations for a hierarchical memory store. The count is well-scoped without unnecessary complexity.

    Completeness4/5

    Core CRUD and browsing are covered. Minor gaps like renaming or moving memories exist, but agents can work around by editing content or using multiple steps.

    Maintenance

    ActivityActive
    ResponsivenessNo issues