菜单
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).
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/strapi/community --skill n8n-start命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| 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).