@tomsmart-ai/mcp-audit-n8n
v0.1.0
Published
MCP server for auditing n8n workflow JSON for AI orchestration anti-patterns. Used internally for AI Orchestration Audit-as-a-Service (AAA) Tier 2-3 deliverables, also usable standalone.
Maintainers
Readme
@tomsmart-ai/mcp-audit-n8n
MCP server for auditing n8n workflows. Built for AI Orchestration Audit-as-a-Service deliverables. Open-source MIT.
Point this server at an n8n workflow JSON export and it returns:
- Anti-pattern findings (missing error handlers, hardcoded API keys, weak prompts, unauthenticated webhooks)
- Monthly cost estimate at given execution rate (with explicit assumptions)
- Recommendation on whether to keep vanilla n8n or pair-program with Claude Code
Tools
audit_workflow_json
Surfaces:
- HIGH: missing Error Trigger node despite AI nodes present, hardcoded API keys in node parameters, unauthenticated webhook nodes
- MED: AI nodes without
continueOnFail/onErrorconfig, weak LLM prompts (< 50 chars), HTTP nodes without retry/timeout - LOW: high temperature without justification (> 0.9), missing executionOrder setting
Knows about LangChain package nodes (@n8n/n8n-nodes-langchain.openAi, .anthropic, .lmChatAnthropic, .agent, .chainLlm, etc.) NOT just legacy n8n-nodes-base.* types.
cost_estimate_workflow
Returns monthly USD estimate at given executions_per_month. Includes explicit warning about pricing snapshot age + unmodeled cases (loops, tool calls, prompt length variance). Add 20-30% buffer when quoting clients.
pair_pattern_check
Heuristic recommendation:
- n8n-only-ok if workflow is simple orchestration without much AI complexity
- hybrid if medium AI complexity — extract AI step to Claude Code-managed MCP server, n8n calls via HTTP
- use-claude-code-pair if 3+ AI nodes + 2+ Code nodes — split: n8n handles orchestration, Claude Code-managed service handles AI logic
Install
npm install -g @tomsmart-ai/mcp-audit-n8nUse with Claude Code
{
"mcpServers": {
"audit-n8n": {
"command": "mcp-audit-n8n"
}
}
}Then ask Claude:
Audit my n8n workflow at /path/to/workflow.json — find anti-patterns + estimate cost at 1000 executions/month.Claude calls audit_workflow_json + cost_estimate_workflow and reports findings.
Source data
Workflow JSON is the standard n8n export format. To get it: open workflow in n8n UI → 3-dot menu → Download → JSON.
The tool reads but never modifies the file. No telemetry, no external API calls except optional LLM categorization (which is opt-in for the future v0.2 release).
Roadmap
- v0.1.0 (today, Wt 26.05.2026) — audit_workflow_json + cost_estimate_workflow + pair_pattern_check
- v0.2.0 — orphan node detection (parse workflow.connections, find unreachable nodes)
- v0.3.0 — credential audit (does referenced credential exist?)
- v0.4.0 — compatibility check (workflow expressions valid in current n8n version?)
- v0.5.0 — pattern catalog: detect known patterns (RAG, agent loop, chatbot, etl) and recommend best-practice variants
License
MIT
Author
Tom Smart — smartflowproai.com · @TomSmart_ai
Pair-built with Claude (Anthropic's coding agent). Tom scoped tools + audit categories from n8n production experience. Claude wrote TypeScript. Tom reviewed every change.
