Skip to main content
Glama
j0hanz

memdb

by j0hanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memdb

No user-submitted related servers found.

    Related Servers

    • tartarus-mcp

      saluca-labs
      A
      license
      Not graded
      quality
      C
      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

    • Memento

      iAchilles
      A
      license
      A
      quality
      C
      maintenance
      A local, fully-offline MCP memory server that enables persistent storage and retrieval of information using SQLite with both keyword and semantic vector search capabilities.
      10
      19 npm
      13
      MIT

    • 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

    • server-memory

      MK-986123
      A
      license
      A
      quality
      C
      maintenance
      A local-first MCP server for durable agent memory using SQLite and FTS5, enabling knowledge graph storage, search, and recall for AI agents.
      20
      1
      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 12 tools

    Disambiguation4/5

    Tools are mostly distinct: CRUD operations, batch variants, search, and relationship operations each have clear roles. The only mild ambiguity is between search_memories and recall, though recall's relationship traversal is explicitly described.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern like store_memory, get_memory, delete_memory, and create_relationship. Minor deviations are 'recall' and 'memory_stats', which are still readable but break the otherwise consistent convention.

    Tool Count5/5

    12 tools is well-scoped for a memory server with knowledge graph features. Each tool covers a distinct operation without bloat or redundancy.

    Completeness4/5

    The memory lifecycle is well covered with single and batch creates/deletes, retrieval, update, search, and stats. Minor gaps include no explicit list-all operation and no update operation for relationships, but these are workable via search and delete/recreate.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources