The /n8n-init command

What the bootstrap command actually does.

Invocation

/n8n-init

Runs in the current working directory. Takes no arguments.

What it asks

Three prompts, one at a time:

1. Project description — your answer is written verbatim into CLAUDE.md. Don't overthink it; 1-2 sentences is enough.
2. n8n URL — the base URL of your n8n instance. Trailing slashes are stripped.
3. n8n API key — sensitive; not echoed back. Written into .mcp.json.

What it writes

./CLAUDE.md

Build-loop manual with your description injected as the project goal. Covers:

• Mandatory build loop (8 steps)
• nodeType format gotcha
• Which skills to invoke for which tasks
• Which subagents are available
• Credentials location and gitignore reminder

./.mcp.json

Registers the n8n-mcp MCP server for this project with your credentials:

{
  "mcpServers": {
    "n8n-mcp": {
      "command": "npx",
      "args": ["-y", "n8n-mcp"],
      "env": {
        "MCP_MODE": "stdio",
        "LOG_LEVEL": "error",
        "DISABLE_CONSOLE_OUTPUT": "true",
        "N8N_API_URL": "<your-url>",
        "N8N_API_KEY": "<your-key>"
      }
    }
  }
}

./.claude/settings.json

Grants default permissions to the read-only and create/update n8n-mcp tools so Claude doesn't prompt on every call. Delete and test operations stay in the "ask" list — you'll be prompted before anything destructive.

./.gitignore

Ensures .mcp.json (which contains your API key) is never committed. Also ignores .env, node_modules/, and *.log.

What it does NOT write

Deliberately, /n8n-init does not create project subfolders like workflows/, evidence/, or docs/. Organize your files however you want — the kit doesn't impose a folder convention.

Pre-existing files

If any of the files above already exist, the command asks before overwriting. This protects your work if you re-run /n8n-init by accident in a folder that's already been bootstrapped.

Re-running

Safe to re-run if you:

• Want to change the project description (re-prompt, rewrite CLAUDE.md)
• Rotated your n8n API key (re-prompt, rewrite .mcp.json)
• Switched to a different n8n instance for this project

Each re-run prompts for overwrite confirmation.

After it runs

Enter plan mode (or the command auto-enters) and describe the workflow you want. The n8n-workflow-builder subagent picks up from there.

Go to Subagents to see how the builder, validator, and deployer agents interact.