Skills

Skill 14 of 42

N8n:setup Mcps

Configure MCP servers for n8n development. Use when the user says /setup-mcps or asks to set up MCP servers for n8n.

1 minute · 297 words · 6 sections

Install

$ npx skills add n8n-io/n8n --skill n8n:setup-mcps

$ npx skills add n8n-io/n8n

» /plugin marketplace add n8n-io/n8n

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

MCP Setup for n8n Development

Configure commonly used MCP servers for n8n engineers.

Instructions

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).

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)

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/mcp

After 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/mcp

After 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/mcp

After adding, tell the user to run /mcp in their next session to authenticate.

After running the commands, confirm which MCPs were configured and note any manual steps remaining (authentication via /mcp, Context7 setup).

Colophon for this issue

Colophon

How this issue was made

Source

github.com/n8n-io/n8n, branch master, last pushed 23 September 2026.

Licence

Other — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

42 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 5 distinct layouts observed: .agents/skills/*/SKILL.md, .claude/plugins/n8n/skills/*/SKILL.md, .opencode/skills/*/SKILL.md, packages/@n8n/cli/skills/*/SKILL.md, packages/@n8n/instance-ai/skills/*/SKILL.md.

Authorship

10 of 42 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 10°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “6 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

50 editorial notes across 25 of 42 skills. They are printed in the margin of each skill rather than as errors here.

N8n:content Design — 2 notes
N8n:conventions — 2 notes
N8n:create Community Node Lint Rule — 2 notes
N8n:create Issue — 2 notes
N8n:create PR — 2 notes
N8n:create Skill — 2 notes
N8n:db Migrations — 2 notes
N8n:linear Issue — 2 notes
N8n:loom Transcript — 2 notes
N8n:node Add OAuth — 2 notes

and 15 more.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude/plugins/n8n/.claude-plugin/marketplace.json by n8n, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /n8n-io/n8n.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

MCP Setup for n8n Development

Configure commonly used MCP servers for n8n engineers.

Instructions

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).

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)

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/mcp

After 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/mcp

After 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/mcp

After adding, tell the user to run /mcp in their next session to authenticate.

After running the commands, confirm which MCPs were configured and note any manual steps remaining (authentication via /mcp, Context7 setup).