/setup-mcps
Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n.
$ npx -y skills add n8n-io/n8n --skill setup-mcps --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/setup-mcps
Context preview
The summary Claude sees to decide when to auto-load this skill.
Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n.
SKILL.md
setup-mcps.SKILL.mdname: 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.
MCP Setup for n8n Development
Configure commonly used MCP servers for n8n engineers.
Instructions
1. First, check which MCPs are already configured by running:
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:
- Linear: `mcp.linear.app`
- Notion: `mcp.notion.com`
- Context7: `ctx7` or `context7-mcp`
- Figma: `mcp.figma.com`
Skip any MCP whose URL/command is already present (regardless of scope or name).
2. Present the MCP selection menu using `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) |
3. Process each selected MCP **one at a time** in a loop. For each MCP: a. Ask the user via `AskUserQuestion`: "Where should **{MCP name}** be installed?"
- **user** (default, recommended) — available in all projects
- **local** — only in this project
b. Run the install command for that MCP with the chosen scope c. Then move to the next MCP and ask again
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:
Linear
claude mcp add -s {scope} linear-server --transport http https://mcp.linear.app/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
Notion
claude mcp add -s {scope} notion --transport http https://mcp.notion.com/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
Context7
Tell the user to run this command themselves (it handles auth via OAuth automatically):
npx ctx7 setup --claude
Figma
claude mcp add -s {scope} figma --transport http https://mcp.figma.com/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
5. After running the commands, confirm which MCPs were configured and note any manual steps remaining (authentication via `/mcp`, Context7 setup).
Read more
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.
MCP Setup for n8n Development
Configure commonly used MCP servers for n8n engineers.
Instructions
1. First, check which MCPs are already configured by running:
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:
- Linear: `mcp.linear.app`
- Notion: `mcp.notion.com`
- Context7: `ctx7` or `context7-mcp`
- Figma: `mcp.figma.com`
Skip any MCP whose URL/command is already present (regardless of scope or name).
2. Present the MCP selection menu using `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) |
3. Process each selected MCP **one at a time** in a loop. For each MCP: a. Ask the user via `AskUserQuestion`: "Where should **{MCP name}** be installed?"
- **user** (default, recommended) — available in all projects
- **local** — only in this project
b. Run the install command for that MCP with the chosen scope c. Then move to the next MCP and ask again
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:
Linear
claude mcp add -s {scope} linear-server --transport http https://mcp.linear.app/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
Notion
claude mcp add -s {scope} notion --transport http https://mcp.notion.com/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
Context7
Tell the user to run this command themselves (it handles auth via OAuth automatically):
npx ctx7 setup --claude
Figma
claude mcp add -s {scope} figma --transport http https://mcp.figma.com/mcpAfter adding, tell the user to run `/mcp` in their next session to authenticate.
5. After running the commands, confirm which MCPs were configured and note any manual steps remaining (authentication via `/mcp`, Context7 setup).
Fair-code platform to build and deploy AI agents and workflows. Combine a visual canvas with custom code, run it self-hosted or in the cloud, and connect to 1500+ integrations. AI automation you can trust with real work, from prototype to production.
Repo: n8n-io/n8n
Other skills on n8n.
- /n8n-cli
Use the n8n CLI to manage workflows, credentials, executions, and more on an n8n instance. Use when the user asks to interact with n8n, automate workflows, manage credentials, or operate their instance from the command line.
Open skill - /agent-builder
Load before calling build-agent for a new or existing n8n Agent. Governs prerequisite creation, faithful handoff of the user's request, agent targeting across turns, builder questions, testing, and publishing. Use directly for routine follow-ups when the conversation already
Open skill - /config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the
Open skill - /credential-recipe-research
Lookup procedure for Simplified Custom Auth recipe fields — sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl from the provider's real documentation instead of memory. Load before composing credentialHints for a service without a dedicated
Open skill - /credential-setup-with-computer-use
Guides n8n credential setup through Computer Use browser tools. Use when a user needs OAuth apps, API keys, client IDs, client secrets, or other credential values from an external service console.
Open skill - /data-table-manager
Load before calling data-tables or parse-file. Use for natural standalone requests like "what data tables do I have?", "show/list my tables", or "what columns are in this table?", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up,
Open skill

