How do I connect Infernoflow MCP Server to Claude?

Run `claude mcp add infernoflow -- npx -y infernoflow` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Infernoflow MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Infernoflow MCP Server do?

Infernoflow MCP Server documents 10 tools to the agent, including amp_bookmark, amp_handoff, amp_health. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Infernoflow

Unclaimed

by ronmiz

Persistent memory for AI coding sessions — captures what agents can't infer from code alone. Works with Copilot, Cursor, Claude, and Windsurf

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'infernoflow' -- 'npx' '-y' 'infernoflow'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

agent-handoffai-memorycopilotcursordeveloper-toolsmcp-serverpersistent-memorysession-memory

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

10 of 10 tools

Documented tools (10)

From project documentation. A server handshake does not verify each tool’s description or behavior.

amp_bookmark

🆕 Drop a named resume point — auto-captures the current session transcript when no note is given

amp_handoff

Generate the handoff document for the next AI session

amp_health

Session health score (A–F)

amp_read

Read entries with optional filters

amp_search

Keyword search across entries

amp_write

Log an entry (type, msg, optional file / line / tags / detail)

infernoflow_check

Validate the capability contract (read-only)

infernoflow_context

Generate AI-ready context for a task

infernoflow_git_drift

Detect which capabilities recent commits affected

infernoflow_status

Memory + project health at a glance

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Infernoflow MCP Server

How do I connect Infernoflow MCP Server to Claude?: Run `claude mcp add infernoflow -- npx -y infernoflow` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Infernoflow MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Infernoflow MCP Server do?: Infernoflow MCP Server documents 10 tools to the agent, including amp_bookmark, amp_handoff, amp_health. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.