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.17723 PyPI883MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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.7 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.9 npmISC

LogNexusofficial
AlicenseAqualityBmaintenanceUniversal 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.612730 npm6MIT- AlicenseNot gradedqualityDmaintenanceProvides 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
Each tool targets a fairly distinct operation: write/read/search/bookmark/resume/handoff cover the memory lifecycle, while git_drift and status cover project-level health. The main overlap is between amp_health (session health score) and infernoflow_status (project memory + contract health 'at a glance'), and amp_resume vs amp_read are close since resume is a composite view over the same entries. Descriptions do enough to steer selection, but the health/status pair could be confused.
All nine names follow a snake_case verb_noun pattern (amp_bookmark, amp_write, infernoflow_git_drift), which is predictable and readable. The only deviation is the split between the amp_ and infernoflow_ prefixes, which implies two namespaces inside a single server and slightly muddies grouping. Internally each prefix is consistent, so this is a minor deviation rather than a mixed-convention problem.
Nine tools is well within the ideal 3-15 range for a session-memory server. Each tool maps to a concrete step in the workflow (capture, retrieve, summarize, health-check) with no filler entries. Nothing appears redundant enough to be pruned.
The capture-and-retrieve surface is solid: write, read, search, bookmark, resume, handoff, plus health and drift diagnostics. However there is no update or delete/forget operation, so a wrong or stale memory entry cannot be corrected or removed — only appended to, which is a notable gap for a memory store. Listing or pruning bookmarks is also absent.