Skip to main content
Glama

Related Servers

Alternatives to Loci

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.
      12
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
      13 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.
      45 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent, cross-session memory for MCP-compatible AI tools, letting them store and share a unified local memory with Chinese-aware semantic search, typo correction, associative perception chains, and graph-based recall.
      154 npm
      3
      -

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Each tool has a distinct layer+action scope: memory_* tools target the memory store, session_* tools target archived conversation text, and panel_open is a UI action. The only mild overlaps are memory_list vs memory_context (recent vs resident context) and memory_handoff vs memory_context, but the descriptions clarify their different outputs and use cases.

    Naming Consistency4/5

    Nearly all tools follow a predictable domain_action pattern (memory_save, memory_search, session_save, session_recall). Minor deviation: verbs mix actions (save/list/search) with nouns (stats/context/handoff), though it stays readable and consistent in style.

    Tool Count5/5

    11 tools is well-scoped for a cross-agent memory system, covering listing, saving, searching, deleting, stats, pinning, context retrieval, session archive/recall, handoff, and panel access. Each tool earns its place with no obvious redundancy.

    Completeness4/5

    Strong lifecycle coverage across both memory and session layers, including soft delete and pin/unpin toggle. The notable gap is a memory_update/edit operation — editing requires delete-then-save — and there is no direct get-by-id retrieval, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues