n8n's official Claude Code connector can now create and edit workflows! This goes way beyond plugging an API into MCP. It's purpose built for LLMs. Includes a new workflow TypeScript SDK so workflows are written as code instead of JSON, with more reliable validation. Works anywhere MCPs are supported... (n8n 2.18.5+). 🔗 Full video:show more

Lol, weird that you just found out about this.. Third Party MCP was even working way better than your official n8n MCP 😫

This is exactly what AI native tools should look like, not just another API wrapper but actually built for how LLMs think. Game changer for anyone building serious automations.

Ship one workflow with guardrails, logging, and ROI tracking, then scale — otherwise it's demo theatre.

Bit late to it mate

This is huge! The shift from JSON to proper TypeScript workflows with reliable validation is going to change how teams build agents. Tried it yesterday, Claude literally debugged and improved my flow in one go. Mind blown. Any plans to expand this to other frontier models soon?

TypeScript SDK over JSON edits is the right call. JSON editing through Claude was workable but you spent 30% of the time fixing node IDs and credential refs. Code-first with validation closes the loop. Will try this on a 35-node intake flow tomorrow.

I think this is cool but the reality is why not just write TS directly and skip n8n as an intermediate completely. Not saying this to be contrarian but you guys need to fundamentally create an agent native product. Ditch the canvas

the purpose-built workflow type is the part that matters. mcp through n8n is fine for triggers but creating/editing flows from an llm needs structured intermediates the model can actually reason about, not just json string handoffs. curious which intermediate format you landed on.

This is where MCP gets real. Not another connector badge, but a way for the agent to change the thing and leave something a human can inspect after.

Claude Code creating and editing n8n workflows directly is the automation loop I didn't know I needed 👀

Is this available for Codex CLI and Codex App?

workflows in a matter of hours. n8n and Claude are changeing the industry. but so few businesses use workflows. yet the potential is insane. whether your a small or a big business. check out my profile and get ahead the curve.

Claude Code + n8n building workflows automatically?? Automation just automated itself 🤯

Used this last night, and I'm impressed.

Great work

People still using n8n?

@KevinGeffen

Crazy stuff. Faster, better, simpler.

新しいClaude Codeコネクターは素晴らしいですね！ワークフローがコードで書かれるようになるのは、より信頼性が高いですね。ありがとうございます！

"That's amazing news! The Claude Code connector is a game-changer for n8n users. This level of customization and reliability will take workflow automation to the next level. Can't wait to see what you build with it!"

That's awesome! Love seeing tools evolve like this. Makes building workflows so much smoother. Excited to see what people create!

n8n + Claude MCP for workflows is ⚡—we took this further for job search. Placed MCP: AI agent auto-searches roles, matches your CV & drafts apps inside Claude. Drop your email → 7-day Pro free: #PlacedMCP

The TypeScript SDK is the bit I’d watch. JSON-generated workflows usually look fine until validation or runtime edges. If agents are writing against typed primitives, review and rollback should get a lot less painful.

Now do Hermes.

This shifts n8n from automation tool to full agent builder curious how stable the workflow generation is in production

I can't use hermes to connect to mcp server. Please help!

Amazing 🔥❤️

typescript sdk rocks

Hahahaha Claude doing workflows alone

Now we talking!!

this is the right abstraction shift. agents shouldn’t be editing random workflow JSON in production. they need code, validation, and a diff a human can review before the workflow starts doing real work

Love it...nice work! 💪

Interesting