An MVP? Definitely not. A prototype maybe, but...

For building a prototype, unless you have the discipline to not put the prototype into production and your organization has similar discipline, I wouldn't recommend vibe coding. We all know how hard it can be to convince management that he amazing thing they're using right this moment needs to be scrapped and rewritten because the insides are garbage.

No-code tools are better suited and safer to use in that respect.

This is true, except that in my experience, senior management seems to have a real hard time, differentiating between “ship-quality, but sparse, MVP,” and “lash-up, crap-quality prototype.”