القائمة
Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n.
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first. Do NOT use for new one-off workflows, single-workflow edits, verification-only requests, or standalone data-table ops — use workflow-builder or data-table-manager instead.
Default path for all single-workflow work: new one-off workflows, existing- workflow edits, verification repairs, and workflow-local data tables. Use build-workflow directly — do not load planning or create-tasks first. Load planning only when multiple coordinated workflows or shared cross-task data tables require a dependency-aware task graph.
Designs and manages n8n Data Tables directly with the data-tables and parse-file tools. Use when the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV/XLSX/JSON attachments, and before building or planning workflows that create or write to Data Tables.
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, or empty parameter values after a successful run.
Handles system follow-up turns: planned-task-follow-up (synthesize, replan, build-workflow, checkpoint), background-task-completed, running-tasks context, create-tasks silence rules, and detached delegate completion. Load whenever any of these tags appear or after spawning create-tasks or delegate.
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
| name | n8n:setup-mcps |
| description | Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n. |
Configure commonly used MCP servers for n8n engineers.
claude mcp list
Parse the output and match by URL/command, not server name (users may have used different names). The URLs to check for:
mcp.linear.appmcp.notion.comctx7 or context7-mcpmcp.figma.comSkip any MCP whose URL/command is already present (regardless of scope or name).
AskUserQuestion with multiSelect: true.
Only show MCPs that are not already configured. If all are already configured,
inform the user and skip the menu.| Option | Label | Description |
|---|---|---|
| Linear | Linear | Linear ticket management (HTTP, OAuth — opens browser to authenticate) |
| Notion | Notion | Notion workspace integration (HTTP, OAuth — opens browser to authenticate) |
| Context7 | Context7 | Library documentation lookup (OAuth setup via CLI) |
| Figma | Figma | Figma design integration (HTTP, OAuth — opens browser to authenticate) |
AskUserQuestion: "Where should {MCP name} be installed?"
Do NOT batch the scope question — ask separately for each MCP.
Do NOT offer project scope — it modifies .claude/settings.json which is tracked in git.
Commands per MCP:
claude mcp add -s {scope} linear-server --transport http https://mcp.linear.app/mcp
After adding, tell the user to run /mcp in their next session to authenticate.
claude mcp add -s {scope} notion --transport http https://mcp.notion.com/mcp
After adding, tell the user to run /mcp in their next session to authenticate.
Tell the user to run this command themselves (it handles auth via OAuth automatically):
npx ctx7 setup --claude
claude mcp add -s {scope} figma --transport http https://mcp.figma.com/mcp
After adding, tell the user to run /mcp in their next session to authenticate.
/mcp, Context7 setup).