Skip to main content
Glama

Related Servers

Alternatives to afair

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Self-hosted, local-first knowledge graph and memory server for AI agents. Enables agents to persist, recall, and organize knowledge through MCP with automatic distillation, deduplication, and cross-linking.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open memory standard for AI agents. Local-first, MCP-native, lives in your Obsidian vault. Bi-temporal markdown, hybrid retrieval, reproducible benchmark.
      345 PyPI
      16
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Open-source MCP memory server providing persistent, cross-platform context for AI tools via a knowledge graph with encrypted storage.
      10 npm
      13
      AGPL 3.0

    TDQS

    A4.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a completely distinct and clear purpose: remember saves user facts, recall retrieves them, and observe logs agent actions. There is no possible confusion between the tools.

    Naming Consistency5/5

    All three tool names are imperative verbs (remember, recall, observe) that directly describe their action, forming a consistent and predictable pattern. No naming convention conflicts.

    Tool Count5/5

    Three tools is exactly right for a memory vault server: one to write user memories, one to read them, and one to log agent activity. Each tool earns its place without any redundancy or scope creep.

    Completeness5/5

    The tool set covers the full memory lifecycle: creation (remember), retrieval/search (recall), and agent activity logging (observe). There are no obvious gaps—the domain is self-contained and complete for a vault that persists across sessions.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week