I will somewhat disagree: I think it's always a good idea to apply good patterns to even simple problems.
But I agree that it must be done carefully. Applying a bloated framework like Struts to a simple web app is a bad idea (actually, I'm on record as asserting that applying a bloated framework like Struts to any app is a bad idea -- but that's another show).
It's quite possible to apply proper patterns without code bloat. Sure you might end up with a greater total line count than without, but that's far less important than a good organization and structure.
I do not think you can really go wrong with good MVC practices.
As with anything, get comfortable with the (MVC) concepts. Think of how you would do it and why it makes sense. THEN, not before, go and see what offerings there are. If you come to your own conclusions it will be much easier to evaluate API/Frameworks that are available.
Many available API/Frameworks will try to 'sell' themselves with a quick 'we offer MVC' explanation without really telling how they do it or why it's better than just good practice. Also, many people will all but dress in white robes with little armbands and tout how much they like framework A over framework B. Don't get caught up in that, it's such a waste of time in my opinion.