infernoflow
Related Servers
Alternatives to infernoflow
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.17534 PyPI866MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with git-native persistent memory and a dependency-aware task graph, letting them record and fuzzy-recall architectural decisions, lessons, and gotchas while creating, claiming, and completing tasks that auto-unblock downstream work. Stores everything as plain JSON and Markdown committed inside the repository, so context stays branch-aware, team-shared, and reviewable in pull requests.9 npmMIT
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents persistent, branch-aware memory and a dependency-tracked task graph by storing decisions, lessons, and tasks as plain JSON and Markdown committed directly into the repository. Agents can record and fuzzy-search past decisions, dump instant project context, and create, claim, complete, and query tasks whose completion automatically unblocks downstream work.MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent cross-session memory by storing atomic markdown knowledge cards with bidirectional wiki-links that agents recall before starting work. Syncs across clients and devices via git without any vector database or embeddings.4 npmISC

LogNexusofficial
AlicenseBqualityAmaintenanceUniversal Git-powered persistent memory, context rules & native MCP server for AI coding agents. Prevents context amnesia with stateful workflows, Git Notes, and cross-model review gates across Claude, OpenAI, Gemini & DeepSeek in Cursor, Claude Code & VS Code.61204MIT- AlicenseNot gradedqualityCmaintenanceProvides a memory layer for AI coding agents with Git-powered version control, enabling automatic tracking of prompts, context, and code diffs.194MIT
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.