메뉴
Start the local n8n instance for the Strapi community hub. Use when the user asks to start, launch, bring up, or run n8n or the automation stack. Pass --mcp to also bring up n8n-mcp (requires N8N_API_KEY and MCP_AUTH_TOKEN in .env).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Show the health and status of the local n8n automation stack. Use when the user asks about n8n status, health, whether it is running, or which containers are up.
Export all workflows from the local n8n instance into version-controlled JSON under apps/automation/workflows/. Use when the user asks to export, pull, snapshot, or sync workflows from the local n8n.
Import workflows from apps/automation/workflows/ into the local n8n instance. Use when the user asks to import, push, load, or sync workflow JSON files to the local n8n.
Restart the local n8n automation stack, preserving whatever profile (plain or mcp) is currently running. Use when the user asks to restart, reload, or reboot n8n.
Stop the local n8n automation stack. Use when the user asks to stop, shut down, halt, or bring down n8n. Data in the n8n_data volume persists across stops.
Domain-expertise guide for designing, building, validating, and modifying n8n workflows using the n8n-mcp tools. Use whenever the user asks to build, create, design, edit, or validate an n8n workflow. Requires the n8n-mcp server to be running (see n8n-start).
| name | n8n-start |
| description | Start the local n8n instance for the Strapi community hub. Use when the user asks to start, launch, bring up, or run n8n or the automation stack. Pass --mcp to also bring up n8n-mcp (requires N8N_API_KEY and MCP_AUTH_TOKEN in .env). |
Starts the n8n container(s) defined in apps/automation/docker-compose.yml via the engine-agnostic scripts/compose.sh wrapper (autodetects Docker or Podman).
Change to the automation directory. All commands below run from apps/automation/.
Ensure .env exists:
test -f apps/automation/.env || cp apps/automation/.env.example apps/automation/.env
If it was just created, tell the user and point them at apps/automation/.env.example.
Decide on MCP. If the user's request didn't specify, ask whether to include n8n-mcp. Default is no.
If starting with MCP, pre-check required env vars:
grep -E '^(N8N_API_KEY|MCP_AUTH_TOKEN)=.+' apps/automation/.env
Both must be non-empty. If either is missing, stop and explain:
MCP_AUTH_TOKEN — generate with openssl rand -hex 32.N8N_API_KEY — chicken-and-egg: start n8n first (without --mcp), create the key in the UI at http://localhost:5678/settings/api, paste it into .env, then run n8n-start --mcp.Start the stack:
# without MCP
pnpm --filter automation n8n:up
# with MCP
pnpm --filter automation n8n:up:mcp
Tail startup logs briefly to confirm health:
pnpm --filter automation n8n:logs --tail=20 &
# (stop after a few seconds)
Or run pnpm --filter automation n8n:ps to confirm the containers are running / healthy.
Report URLs to the user:
If the mcp profile was started, also remind the user that Claude Code must be registered against the MCP server to actually use it. Point them at the "Connecting Claude Code to the local n8n-mcp" section of apps/automation/README.md. The one-line summary:
claude mcp add --scope project --transport http n8n-mcp http://localhost:3100/mcp --header "Authorization: Bearer \${MCP_AUTH_TOKEN}" (writes .mcp.json; export MCP_AUTH_TOKEN before launching claude).--scope project and with the literal token inlined.Skip this reminder if the user has clearly registered it already (e.g. they're invoking an n8n-* tool and it's responding).