I have used both - so here is my opinion on both the stacks.
Meteor is very good for building realtime apps. In meteor your database (MongoDB) is realtime - so all your connected users see the updated data. There is no need of any extra work like setting up sockets and other stuff.
Both Client and Server share the same code which means the amount of coding needed to achieve something is reduced. What took weeks will now take days or even hours to implement.
Meteor has got good community support and the development is going on actively. More and more people are collaborating to release libraries for Meteor. So, no doubt you will get good support from the proactive community.
So, the tldr is that if you are developing a realtime app and you are eager to try out something exciting then go for Meteor.
MEAN stack is older and mature in my opinion. So, naturally you will find a lot of libraries and frameworks to support you. The ecosystem is larger and you will get a lot of help from people around you. If your app is more API driven and doesn't need realtime features (may be very less) you may rather go with MEAN stack.
Both Meteor and MEAN stack use Node.js and MongoDB. So, the only thing that is different is the involvement of Angular in MEAN stack and realtime database in Meteor. If you are a fan of Node.js or server side JavaScript then you can have that in both the stacks. The question is do you want to use Angular on the frontend or just Meteor? This is a matter of preference and the task at hand.
If you have a tight schedule and you are already comfortable with MEAN then you should go for it. Otherwise if you want to learn something new you can try out meteor.
Hope this helps!
May be Evan You (@yyx990803) from Meteor team can give a better comparative analysis. I'll invite him.