Everything depends on the task at hand. There are no exceptions for this proposition for any topic. Be it MVC, Web Design, API programming, or even cooking. That's logic.
In regard to programming, for a particular task MVC may be overkill, or unsuitable. A 100 line script may be faster or more maintainable. Totally depends on task. You dont need to load up a beautifully structured, templated MVC app for an API that is only going to get a piece of data from a db table and serve it to a particular request.
MVC is better in cases that you may reuse the code, or would need to expand it in future, or need to maintain it for any particular reason.
And a note in regard to sequential vs oop - everything happens sequentially in a program. There cannot be two states of the same variable under same conditions. A shopping cart object itself cannot have two values for the same customer with same products with same options with same shipping locations and tax details. Or, you cannot create a shopping cart object and write the products in it before customer actually adds any products to the cart. It would be surreal. Something that requires particular conditions to happen cannot happen without those particular conditions being met, in programming. (And no - just initializing a potential predictive object class for a potential data object is not relevant).
So therefore think practical - do whatever the task in hand and its potential near, mid, and long term requirements necessitate.