~ / rigs / czlonkowski / n8n-mcp

czlonkowski/n8n-mcp

A MCP for Claude Desktop / Claude Code / Windsurf / Cursor to build n8n workflows for you

↗ GitHub ★ 23.0k mit updated 3d ago project Claude CodeCodex
share on X
ARCHETYPE
Orchestrator
A bench of specialised subagents. The main agent mostly delegates.
CONTEXT TAX · EVERY TURN
~3.8k tokens
Moderate · median rig: 2.2k · breakdown
GUARDRAILS
0/5
No committed guardrails · details

Copy this rig

# review before running: this installs third-party code
$ npx degit czlonkowski/n8n-mcp/.claude ./rig-n8n-mcp  # inspect, then merge into .claude/

MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.

$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-agents .claude/skills/n8n-agents
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-binary-and-data .claude/skills/n8n-binary-and-data
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-code-javascript .claude/skills/n8n-code-javascript
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-code-python .claude/skills/n8n-code-python
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-code-tool .claude/skills/n8n-code-tool
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-error-handling .claude/skills/n8n-error-handling
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-expression-syntax .claude/skills/n8n-expression-syntax
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-mcp-tools-expert .claude/skills/n8n-mcp-tools-expert
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-multi-instance .claude/skills/n8n-multi-instance
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-node-configuration .claude/skills/n8n-node-configuration
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-self-hosting .claude/skills/n8n-self-hosting
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-subworkflows .claude/skills/n8n-subworkflows
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-validation-expert .claude/skills/n8n-validation-expert
$ npx degit czlonkowski/n8n-mcp/data/skills/n8n-workflow-patterns .claude/skills/n8n-workflow-patterns
$ npx degit czlonkowski/n8n-mcp/data/skills/using-n8n-mcp-skills .claude/skills/using-n8n-mcp-skills
$ curl -fsSL --create-dirs -o .claude/agents/code-reviewer.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/code-reviewer.md
$ curl -fsSL --create-dirs -o .claude/agents/context-manager.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/context-manager.md
$ curl -fsSL --create-dirs -o .claude/agents/debugger.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/debugger.md
$ curl -fsSL --create-dirs -o .claude/agents/deployment-engineer.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/deployment-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/mcp-backend-engineer.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/mcp-backend-engineer.md
$ curl -fsSL --create-dirs -o .claude/agents/n8n-mcp-tester.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/n8n-mcp-tester.md
$ curl -fsSL --create-dirs -o .claude/agents/technical-researcher.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/technical-researcher.md
$ curl -fsSL --create-dirs -o .claude/agents/test-automator.md https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/test-automator.md

This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 6,413 rigs:

{
  "permissions": {
    "deny": [
      "Read(~/.ssh/**)",
      "Read(**/.env)",
      "Bash(rm -rf *)",
      "Read(./.env)",
      "Bash(rm -rf /)",
      "Bash(git push --force:*)",
      "Bash(sudo *)",
      "Read(**/*.pem)",
      "Bash(rm -rf /*)",
      "Read(~/.aws/**)",
      "Bash(rm -rf:*)",
      "Read(.env)",
      "Bash(git push --force*)",
      "Read(**/*.key)",
      "Read(./.env.*)",
      "Read(**/.env.*)",
      "Bash(sudo:*)",
      "Bash(git reset --hard*)",
      "Bash(git reset --hard:*)",
      "Read(.env.*)"
    ],
    "ask": [
      "Bash(git push:*)",
      "Bash(git push *)",
      "Bash(git commit:*)",
      "Bash(rm *)",
      "Bash(rm:*)",
      "Bash(wget *)",
      "Bash(npm publish:*)",
      "Bash(gh pr merge *)",
      "Bash(chown *)",
      "Bash(docker *)"
    ]
  }
}

Skills (15)

Subagents (8)

code-reviewer
model: inherit
Use this agent when you need to review recently written or modified code for quality, security, and maintainability. This agent should be invoked immediately after code changes are made to ensure high
context-managerUse this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent
debuggerUse this agent when encountering errors, test failures, unexpected behavior, or any issues that require root cause analysis. The agent should be invoked proactively whenever debugging is needed. Examp
deployment-engineerUse this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Doc
mcp-backend-engineerUse this agent when you need to work with Model Context Protocol (MCP) implementation, especially when modifying the MCP layer of the application. This includes implementing new MCP tools, updating th
n8n-mcp-tester
model: sonnet
Use this agent when you need to test n8n-mcp functionality after implementing fixes or new features. This agent should be invoked proactively after code changes to validate that the MCP tools work cor
technical-researcherUse this agent when you need to conduct in-depth technical research on complex topics, technologies, or architectural decisions. This includes investigating new frameworks, analyzing security vulnerab
test-automatorUse this agent when you need to create comprehensive test suites, improve test coverage, or set up test automation infrastructure. This includes writing unit tests with mocks, integration tests with t

Similar rigs

copied ✓