Skip to main content
Glama
agentage

@agentage/mcp-memory

Official
by agentage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @agentage/mcp-memory

No user-submitted related servers found.

    Related Servers

    • veriloop

      arvindcr4
      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

    • dek-mcp

      1000bath
      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

    • ebbingflow-mcp

      chanada440824
      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

    • memory-mcp

      KM-it-ops
      A
      license
      Not graded
      quality
      C
      maintenance
      A local stdio MCP server that exposes a shared brain (read/search/write) over ~/.claude/memory, allowing memories written in any agent to be readable and searchable across all three (Claude Code, Cursor, Codex). It provides tools like memory_search, memory_read, memory_write, etc., with no external services.
      17 npm
      MIT

    • juvina-mcp

      1picassoai
      A
      license
      Not graded
      quality
      C
      maintenance
      Bridges stdio MCP clients to the locally installed Juvina memory engine, enabling persistent local AI memory for coding assistants.
      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.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

    Resources