OOP and MVC

I'm a strong believer in object oriented programming for too many reasons to enumerate here. Same for MVC, but mostly in web apps. Recently I realized that if I try to enforce OOP in an MVC framework, most of the logic moves away from the controller (C) to the model (M), since that is my main object that performs the actions. An alternative is to move this logic to helpers/utils, actions that come to help the models inside the controller, but put outside the model file (mainly because a lot of logic in the model files slows down the dev server restart).<p>I feel that something is not right in trying to mix MVC with too much OOP. Does anyone have other points of view?