Skip to main content
Glama
densuke

fuga-memory

by densuke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fuga-memory

No user-submitted related servers found.

    Related Servers

    • l0-memory

      fabriziosalmi
      A
      license
      Not graded
      quality
      B
      maintenance
      Minimal long-term memory MCP server for AI assistants backed by SQLite FTS5 full-text search, optional hybrid vector retrieval, scoped memory graphs, and VSCode extension.
      1
      MIT

    • MemAI

      Filipe-Soares-de-Almeida
      A
      license
      A
      quality
      A
      maintenance
      A long-term memory MCP server for AI agents that stores memories (facts, decisions, etc.) in a single SQLite database with hybrid search and full edit history, ensuring consistency across sessions.
      38
      1
      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

    • supermem

      lamenting-hawthorn
      A
      license
      Not graded
      quality
      B
      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
    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 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: save, search, list sessions, and delete. No overlap or ambiguity in their functionalities.

    Naming Consistency5/5

    All tool names follow the consistent verb_noun pattern (save_memory, search_memory, list_sessions, delete_memory), enhancing predictability.

    Tool Count4/5

    With 4 tools, the set is slightly minimal but covers core memory operations. A few more tools like update or get-by-id could be added, but the current count is reasonable for the domain.

    Completeness3/5

    Missing update and direct retrieval by ID are notable gaps; however, search serves as a retrieval mechanism. The surface covers create, read (via search), and delete, with list_sessions providing session management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources