Skip to main content
Glama
drakejin

memory-mcp

by drakejin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to memory-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-memory

      fellowgeek
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with persistent, long-term memory via OKF-formatted markdown and SQLite indexing, enabling stateful storage, retrieval, and search across sessions.
      6
      218
      MIT

    • openmemkit

      Jlnine
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to maintain a persistent, queryable memory stored as user-owned Markdown files, with dual-channel retrieval (FTS5 and optional semantic search) and an audited write pipeline.
      11
      MIT

    • agtmem-mcp

      ihletru
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to store, search, and retrieve long-term memory as plain Markdown files with a disposable SQLite index, including note management, decision/bug tracking, and codebase symbol lookup via MCP.
      8
      MIT

    • mcp-ltm

      kvas-it
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
      1
      MIT

    • Memento

      fariborzvrm
      A
      license
      A
      quality
      C
      maintenance
      Gives AI coding agents persistent, searchable typed memory stored as plain markdown files, allowing them to record decisions, contracts, tasks, evaluations, and session logs and update entries by id.
      5
      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.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: reindex for maintenance, remember for creation, recall for search, read for retrieval, update for modifications, forget for deletion/lifecycle changes, and status for system overview. No two tools overlap in function; even update's multiple sub-actions are clearly delineated within a single tool.

    Naming Consistency5/5

    All tools follow a consistent 'memory_' prefix with a descriptive verb (remember, recall, read, update, forget, status, reindex). The naming pattern is uniform and predictable, making it easy to infer tool behavior from names alone.

    Tool Count5/5

    Seven tools is an ideal scope for a memory management server. It covers all core CRUD operations, search, maintenance, and status reporting without redundancy or bloat. Each tool occupies a necessary role in the lifecycle.

    Completeness5/5

    The tool set covers the full memory lifecycle: create (remember), retrieve (recall/read), update (update with edit/supersede/state changes), delete (forget with archive/deprecate/purge), plus maintenance (reindex) and oversight (status). Conflict resolution and linking are also supported, leaving no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources