nishant lamichhane

just fixed and rebuilt an entire AI automation flow — without opening the flow editor once

I just fixed and rebuilt an entire AI automation flow — without opening the flow editor once.

Here's what happened:

We have a YouTube script generation pipeline on Serenities. It takes a keyword (or YouTube URLs), generates  an outline, then writes each section with precise word counts. Two branches — one for URLs, one for direct topics.

The URL branch was broken. Not obviously broken. Subtly broken — it was jumping straight from transcript cleansing to a single Claude call with no outline step, no section iteration, no word count targeting. Just a raw prompt that guessed at length every time.

I asked Claude to check it via MCP.

Within seconds it had read the entire flow — every node, every edge, every config. It found:
- A broken template variable resolving to [undefined] instead of the word count
- Extended thinking enabled on a cleansing node (pointless, just burning tokens)
- The URL branch missing 7 nodes that the keyword branch had
- The MCP help guide serving 5 thin topics with almost no real documentation

Then — still without me touching the UI — it:
→ Added 7 new nodes to the URL branch (outline prompt, Claude outline generate, JSON cleaner, iterator,
section prompt, section writer, text aggregator)
→ Rewired all the edges correctly
→ Updated the webhook response to pull from the new pipeline
→ Rewrote all 5 MCP help topics with complete documentation — utility node configs, template variable syntax,
Claude toolInputJson templates, debugging guides, everything

One conversation. Zero UI clicks. The flow went from broken to production-ready.

This is what MCP actually unlocks. Not just "ask AI to explain your code." Ask AI to read your live
infrastructure, reason about what's wrong, and fix it — programmatically, precisely, at the API level.

We built MCP support into Serenities so AI agents can build and manage flows on behalf of users. Today I used
it on our own platform. It worked exactly as intended.

The future of automation isn't drag-and-drop. It's conversational.

14 views

Add a comment

Replies

Be the first to comment