Skip to main content
Glama
MK-986123

server-memory

by MK-986123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to server-memory

No user-submitted related servers found.

    Related Servers

    • tartarus-mcp

      saluca-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.
      1 npm
      1
      Apache 2.0

    • MemoryPatch

      AppleLamps
      A
      license
      A
      quality
      B
      maintenance
      A local MCP memory server for AI agents to manage memory with evidence-backed, versioned mutations, using SQLite with FTS5 for storage and search.
      6
      Apache 2.0

    • MCPSaver

      cpntodd
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent, searchable agent memory using SQLite FTS5, replacing flat MEMORY.md files with efficient full-text search and workspace context caching.
      GPL 3.0

    • agent-memory

      khaled1174
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing persistent memory management for AI agents using SQLite and FTS5, enabling storage, full-text search, and recall of memories with namespace isolation.
      1
      MIT

    • supermem

      lamenting-hawthorn
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server providing persistent AI memory with four-tier retrieval (SQLite FTS5, graph, vector, LLM agent) to give AI assistants structured, long-term memory without RAG.
      1
      Apache 2.0

    • memdb

      j0hanz
      A
      license
      A
      quality
      D
      maintenance
      A SQLite-backed MCP memory server providing persistent memory storage with full-text search and knowledge graph capabilities for AI assistants.
      12
      46 npm
      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

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: CRUD for entities/relations/observations, search, timeline, tags, backup, and context retrieval. The main ambiguity is between memory_context and memory_context_full, which serve the same recall purpose at different verbosity levels, but the descriptions clarify the intended use.

    Naming Consistency4/5

    The majority of tools follow a consistent snake_case verb_noun pattern like create_entities, delete_relations, query_timeline, and export_graph. A few noun-phrase exceptions like memory_context, memory_context_full, and memory_stats break the pattern slightly, but the naming is still predictable and readable.

    Tool Count4/5

    At 20 tools, this is heavier than the ideal 3-15 range, but the extra tools cover distinct supporting functions such as backup, import/export, stats, tags, and timeline queries. No tool feels purely redundant, though the two memory_context variants add some bulk.

    Completeness4/5

    The toolset covers entity/relation/observation lifecycle, search, navigation, activity logging, tags, persistence, and memory statistics. Obvious gaps like explicit entity/relation updating or observation rollback are worked around via delete/recreate and version history, so core workflows are not blocked.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources