n8n-cli-from-mcp
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js · Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: n8n-cli-from-mcp
description: Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n…
category: ai
runtime: Node.js / Python
---
# n8n-cli-from-mcp output preview
## PART A: Task fit
- Use case: Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n8n to run on a schedule or webhook without an agent. Use when productizing an MCP-driven prototype. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Procedure / Output format / Tips” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n8n to run on a schedule or webhook without an agent. Use when productizing an MCP-driven prototype. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Procedure / Output format / Tips” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/n8n-cli-from-mcp`, `/tmp`, `/n8n-cli-document`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Validate with a small run
Start with a small task and check whether the result follows “Procedure / Output format / Tips”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: n8n-cli-from-mcp
description: Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n…
category: ai
source: tomevault-io/skills-registry
---
# n8n-cli-from-mcp
## When to use
- Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n8n to run on a schedul…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Procedure / Output format / Tips” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "n8n-cli-from-mcp" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Procedure / Output format / Tips
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js / Python | read files, write/modify files, run shell commands | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}/n8n-cli-from-mcp — MCP / Skill → n8n Workflow
Take an MCP server config or a Claude Code skill and generate an n8n workflow that does the same thing without needing an agent at runtime.
Procedure
Identify the source:
- MCP server: ask for the server name, command, and tools it exposes (or read from
~/.config/claude/mcp.jsonstyle config) - Claude Code skill: ask for the skill name or path to its SKILL.md
- MCP server: ask for the server name, command, and tools it exposes (or read from
Read the source's actual capabilities:
- For an MCP server: list the tools, their input schemas, what they return
- For a skill: read the procedure section, identify what commands/APIs it calls
Map MCP tools / skill steps to n8n nodes:
- HTTP API call → HTTP Request node
- Slack post → Slack node
- Notion read/write → Notion node
- File read/write → Read/Write Files node
- Code execution → Code node (JS or Python)
- LLM call → OpenAI / Anthropic node
- Branching logic → IF / Switch node
Identify what the workflow's trigger should be:
- If the original MCP/skill was invoked by an agent on demand → Manual Trigger or Webhook
- If it was meant to run on a schedule → Schedule Trigger
- If it was reactive to events → Webhook Trigger or specific event trigger node
Build the workflow JSON:
- Start with the trigger
- Chain the mapped nodes
- Add credentials where needed (use existing instance credentials, not new ones)
- Add error handling for any external API calls
Show the proposed workflow before importing:
- Print the node-by-node plan
- Highlight any places where the mapping is approximate ("MCP tool X has no direct n8n equivalent — using Code node with the same logic")
Import (only after user approval):
n8n-cli wf import /tmp/from-mcp.json(don't activate)- Walk the user through testing it manually first
- Then activate
Output format
- Show the source's tools/steps as a numbered list
- Show the mapped n8n nodes as a parallel numbered list
- Highlight any mappings that need user judgment
- Confirm before importing
Tips
- The most natural conversions are MCP servers that just call HTTP APIs or run scripts — those map 1:1 to HTTP Request or Code nodes.
- MCP servers with deep state (like memory MCPs) don't map well — n8n is stateless between runs unless you wire up a database. Surface this limitation up front.
- Some Claude Code skills are pure prompts (e.g. "summarize this") — those need an LLM node in the n8n workflow, which means a credential and per-run cost.
- For complex MCPs (browser automation, etc.), suggest keeping them as MCPs and having n8n call out to them via HTTP if exposed, rather than rebuilding them.
- Document the resulting n8n workflow with /n8n-cli-document so the team can maintain it without referring back to the original MCP.
Source: 8Dvibes/n8n-cli — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review