infernoflow
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INFERNOFLOW_AGENT | No | Override the automatically detected agent/writer name stamped on memory entries (e.g. claude, cursor, copilot, memory-keeper, hook, human). | |
| INFERNOFLOW_PROJECT_DIR | No | Project folder whose .ai-memory/ the server reads and writes. Defaults to the current directory. |
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 |
|---|---|
| amp_readC | AMP: read session memory entries with optional filters. |
| amp_writeA | AMP: log a new entry. Required: type + msg (one sentence). Optional: file, line, tags, detail. Use 'detail' for a rich multi-paragraph body (repro steps, code, full reasoning, or a session snapshot) — it's stored in a sidecar and loaded on demand, so it never bloats the always-on memory index. |
| amp_searchC | AMP: search entries by keyword. Optional type filter. |
| amp_bookmarkA | AMP: drop a named session bookmark — a resume point. Required: label (short name). Optional: note. If note is OMITTED, the current session transcript is auto-captured as the bookmark's context (the 'save everything here' resume point). Use when the user says 'bookmark this' / 'mark this point', or before a risky change / when the context window is filling up, so the exact state can be recalled later and appears in the next session's handoff. Bookmarks are never auto-pruned. |
| amp_resumeA | AMP: 'where were we?' in one call — the latest resume point with its note, open dead ends (don't repeat them), recent decisions/notes, uncommitted changes, and which memory store this is. Call it at the start of work in a session. Optional: file (rank entries about that file first). |
| amp_handoffB | AMP: generate the handoff document for the next AI session. format=markdown|json (default: markdown). |
| amp_healthA | AMP: get the session health score (0-100, A-F grade). |
| infernoflow_statusC | Show project memory + contract health at a glance. |
| infernoflow_git_driftB | Detect which capabilities may be affected by recent code changes — useful when memory needs branch-aware revalidation. |
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 9 tools
Most tools target clearly distinct operations: bookmark, resume, write, search, handoff. However amp_health and infernoflow_status both report health/status and could be confused, and amp_read vs amp_search vs amp_resume have partially overlapping 'retrieve memory' purposes that rely on descriptions to separate.
Consistent snake_case verb_noun style throughout. The only deviation is the two-prefix split (amp_* for memory ops, infernoflow_* for status/drift), which is readable but slightly inconsistent — infernoflow_status is conceptually an amp operation.
Nine tools is well within the ideal 3-15 range and each maps to a distinct phase of the memory lifecycle (write, read, search, resume, bookmark, handoff, health, drift). No filler tools.
Covers the capture-and-recall lifecycle well, but there is no update or delete/prune operation for memory entries — bookmarks are explicitly never pruned, and stale or erroneous entries cannot be corrected. Agents must work around this by writing corrective entries.