I ran a benchmark that surprised me. Same AI. Same prompt. Two different approaches to building n8n workflows. Here's what happened: n8n MCP / Skills: ⏱ 15+ minutes to generate 🔴 Hit context limits mid-way ❌ Unconnected nodes, validation errors — unusable out of the box n8n-as-code: ⚡ ~3 minutes 🟢 Low token usage ✅ 100% valid, pushed live with no errors The reason isn't the AI — it's the architecture. MCP dynamically fetches node schemas on every call. Constant roundtrips, massive context pollution, and the AI still guesses wrong half the time. n8n-as-code maps the entire n8n node structure as TypeScript in your IDE. Your AI agent has perfect context locally — before it writes a single line. When to use which: → n8n MCP — Quick exploration, simple workflows, no IDE setup needed → n8n-as-code — Complex workflows, team projects, GitOps, production-ready automations Reliable automation isn't about more nodes. It's about tooling that doesn't hallucinate them. Has anyone else here made this switch? Would love to hear what workflows you're building with it.

Earlier, MCP could only run workflows. Now it can actually: - Create workflows - Update workflows This changes how we build automations. 💡 Quick context:Before this, many of us were using the community MCP (czlonkowski/n8n-mcp) to build workflows with AI. Here’s what’s better now: - The AI no longer gets overloaded with all node dataIt only fetches what’s needed → better context, better output - No more guessing parameters or broken JSONIt now uses exact definitions → more reliable workflows - Setup is much simplerNo Docker, no extra service → just enable it in n8n ⚠️ Still some limitations: - You need to manually add credentials - Workflows are ~80% ready (you refine the rest) - Needs public access for tools like Claude / Cursor Overall, this is a big step toward building n8n workflows directly from AI tools without jumping back and forth. Curious — has anyone here tried the new MCP yet?Would love to hear your experience 👇

hi, I built a workflow which listens to a google drive and embeds new documents to pinecone. the problem: When I upload a folder to this google-drive folder, then it does not work. Is there an easy workaround to solve this problem? thanks!

Anyone who have idea how to make credentials properly for personal LinkedIn for automation post.

I tried many nodes to upload images from google drive to shopify by the basis of SKU but its not working. Any help? Its showing the 406 error