Infernoflow runs on your own machine — the client starts it, so there is no endpoint to ping. 42 installs a week from npm. Last commit 24 Oct 2026.
Git-native memory for coding agents: gotchas, decisions and bookmarks as plain text in your repo.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const out = execSync(lookup, { encoding: "utf8", stdio: ["ignore", "pipe", "ignore"] }).trim();
return path.join(dir, slug, "global.jsonl");
return fs.readdirSync(agentsDir)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add infernoflow -- npx -y infernoflow{
"mcpServers": {
"infernoflow": {
"command": "npx",
"args": [
"-y",
"infernoflow"
]
}
}
}[mcp_servers.infernoflow]
command = "npx"
args = ["-y", "infernoflow"]{
"mcpServers": {
"infernoflow": {
"command": "npx",
"args": [
"-y",
"infernoflow"
]
}
}
}{
"servers": {
"infernoflow": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"infernoflow"
]
}
}
}Optional settings from the registry entry, left out of the block above:
INFERNOFLOW_PROJECT_DIR (Absolute path of the project whose memory to use. Defaults to the open workspace folder).
Alternatives to Infernoflow
same job, measured the same wayPersistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.
Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.
One memory for every AI you work with: your rules, notes and decisions in your own Git repo.
Markdown memory for coding agents that audits itself: drift reports and session digests.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
Team-aware memory: intent, decisions, real-time conflicts for AI coding assistants.
Project memory across sessions for AI agents. A queryable decision log in the repo.
Infernoflow — questions
Answers built from our own checks of this server.