Skip to main content
Glama
Phygital Engram

Phygital Engram

Official

Related Servers

Alternatives to Phygital Engram

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Gives AI agents fast, read-only access to a local knowledge base of Markdown notes and other text documents via a SQLite full-text index. Enables ranked section-level search, reading whole notes or single sections, heading outlines, note listing, and link/backlink navigation without slow disk walks.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to run semantic search over local Obsidian or Markdown vaults, returning notes ranked by meaning with paths, headings, scores, and snippets, and to trigger incremental reindexing of changed notes. Everything runs on the user's own machine, so no note content leaves it.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Gives AI agents a long-term memory layer over plain Markdown notes, letting them run ranked, citable searches, record new facts, and inspect conflicts and stale entries. Results carry freshness labels, supersession history, and audit fields like search timestamp and no-match status so agents can prove a search actually ran.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to search, read, and safely edit a single folder of Markdown notes over HTTPS, with fast full-text search, conflict-guarded edits, link-preserving moves, and a trash folder with restore. It runs self-hosted in Docker next to the notes and keeps strict boundaries around the mounted vault.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to search, read, and navigate a folder of Markdown notes as a knowledge base, with full-text search, backlinks, tags, metadata, and note resources for conversation attachment.
    1
    MIT

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation4/5

The four tools split cleanly by input contract: search_notes takes a query, open_result and around_result take a result id, and check_index takes nothing. The only soft overlap is between open_result and around_result, since both return note text for an id, but the descriptions explicitly separate 'full section' from 'surrounding context' and even state that around_result does not search.

Naming Consistency4/5

All four names are snake_case verb_noun pairs (search_notes, open_result, around_result, check_index), matching the expected pattern. The minor deviation is 'around_result', which uses a preposition rather than an action verb and shifts the object noun from 'notes' to 'result'.

Tool Count4/5

Four tools cover a tight read-only retrieval loop — discover, open, expand context, verify health — and each earns its place with no redundant surface. It sits at the low end, but nothing feels gratuitous; the only pressure toward a fifth tool is a browse/list path that doesn't exist.

Completeness4/5

The stated purpose (search a person's notes and open what you find) is fully covered, including context expansion and a self-diagnostic for stale or private content. The gap is enumeration: there is no way to list recent notes, browse by date, or enumerate people/tags, so questions like 'what did I work on last week' depend entirely on guessing search terms, only partly mitigated by around_result returning same-day notes.

Maintenance

ActivityMaintained
ResponsivenessNo issues