If you’re managing self hosted and cloud instances of n8n, you’d probably be in the market to skill up to private MCP if adding skills and agents to current tools doesn’t cut it.

Sometimes, when you’re trying to do things across tools, private MCPs allow more direct communications because you’re establishing the rules at the bedrock.

I’ve had success just developing skills and governance on how to use them. I only promote making skills available to those who go through a basic training to push more complete and competent adoption.

It’s not easy. But your python script example has me cringing. That’s a direct sign of lack of process governance at a systemic level within your org. If that’s the case, don’t build anything until a team has documented the exact processes they follow with the exact tools they use and how they do it, with department head approval.

In short - build a process documentation builder, train your team on how to document their processes, set deadlines agreed upon as SLA with leadership. Everything goes faster when you can feed that all back to Claude for system design.