Phygital Engram
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGRAM_DATA | Yes | Path to a separate folder where Phygital Engram keeps its own index and files. It must be outside your notes folder. | |
| ENGRAM_VAULT | Yes | Path to your folder of Markdown notes (the vault) to search. It must contain a file named CLAUDE.md at the top, which can be empty. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_notesA | Search the person's Markdown notes with plain words and get a short ranked list. Use it first, before you answer about their past work, projects, decisions, people or notes. Read-only. Each result has an id, the note path, the heading, the date, a snippet and a line saying why it came back (for example an exact match or a decision note). Results can include a private note marked LOCKED: tell the person it exists and let them open it. Pass an id to open_result for the full text. If nothing matches, the list is empty. |
| open_resultA | Open one result from search_notes by its id and return the full section of the note, or the whole note if it is short. Read-only. Use it after search_notes, when a snippet is not enough to answer. An id that no longer exists returns a not-found message: search again. A LOCKED private note is refused, and the person must open it themselves. |
| around_resultA | Show the sections just before and after one result from search_notes, plus other notes written the same day. Read-only. Use it when a result looks right but you need the context around it, such as the step before a decision or the rest of a day. It does not search: it needs a result id. |
| check_indexA | Report whether the search index is fresh, whether anything private slipped in, and whether searches are fast. Read-only: it changes nothing and needs no input. Use it when results look old or missing, or when the person asks if search is healthy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: search_notes finds results, open_result expands one result, around_result provides surrounding context, and check_index reports index health. The descriptions explicitly state when to use each and how they chain, leaving little room for misselection.
All names use consistent snake_case and a short two-word form, mostly following an action_noun pattern (search_notes, open_result, check_index). The exception is around_result, where 'around' is positional rather than a verb, but it remains readable and predictable.
Four tools is a well-scoped set for a read-only note-search server, with each tool covering a distinct step in the retrieval workflow. There is no redundant or obviously missing tool for the core purpose.
The surface covers the key lifecycle of searching, opening, inspecting context around, and checking search health. Minor gaps exist, such as no explicit way to list recent notes or filter searches by date, but agents can largely work around these through search and around_result.