n8n-mcp creates blank nodes instead of AI Agent / Basic LLM Chain nodes?
Using n8n-mcp (July 2025, before v2.22.4) with Claude Code and Cursor, I explicitly request three AI Agent nodes or a Basic LLM Chain node, but it creates blank square nodes and separate disconnected nodes instead. Why does this happen and how do I get proper AI Agent nodes?
Originally asked on GitHub: https://github.com/czlonkowski/n8n-mcp/issues/93
4 answers
Fixed. This was a genuine bug in n8n-mcp, resolved in October 2025 and released in v2.22.4. The maintainer diagnosed the root cause:
NodeTypeNormalizerconverted nodes to their SHORT form while validation expected the FULL form, so AI validation was silently skipped and AI Agent / Basic LLM Chain requests fell back to blank regular nodes. The fix (commits 2627028, 92eb4ef, 36dc8b4) added 13 AI tool validators, an AI Node Validator with 8 checks, and langchain expression validation, so AI nodes are now recognized, schema-validated, given proper tool configurations, and connected with AI connection types (39 validator tests pass).To get correct AI Agent / LLM Chain nodes:
- Update n8n-mcp to v2.22.4 or later — the fix is included there.
- If you're stuck on an older version, one user reported that explicitly asking for
AI Agent node version 2.2in the prompt worked consistently as a workaround. - If you still see blank nodes, capture and share the Claude/MCP tool-call logs; the maintainer requested those logs to diagnose the root cause.
General advice: n8n has multiple AI Agent node versions, so including the exact node version name in your request reduces ambiguity even with the fix in place.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Reporter asked Claude Code and Cursor to create 3 AI Agent nodes (also tried Basic LLM Chain), specifying LLM, tools, and system prompts. The MCP server instead created blank square nodes, split separate nodes, and produced missing connections.
Source: https://github.com/czlonkowski/n8n-mcp/issues/93 (opens external site)
Did this work for you?What @mondi31 tried on GitHub (Worked)
A commenter said they consistently got correct behavior before the official fix by explicitly wording the prompt as "AI Agent node version 2.2".
Source: https://github.com/czlonkowski/n8n-mcp/issues/93#issuecomment-3125237711 (opens external site)
Did this work for you?What @czlonkowski tried on GitHub (Outcome unclear)
The maintainer asked the reporter to share Claude logs to see what was sent under the hood; no outcome was reported in the thread.
Source: https://github.com/czlonkowski/n8n-mcp/issues/93#issuecomment-3116705374 (opens external site)
Did this work for you?
Related questions
- n8n-MCP: complex Claude Desktop workflows won't open in n8n UI — 'propertyValues is not iterable'?
- n8n-mcp partial update fails: 'Cannot convert undefined or null to object' (Claude Desktop/Cursor)
- n8n-mcp n8n_update_partial_workflow updateNode fails with "Cannot convert undefined or null to object"
- n8n-mcp Docker: missing BACKEND_SUPABASE_URL after pulling latest image
- n8n_update_partial_workflow fails: "settings must NOT have additional properties"