You don't need DI tool in this scenario since MEF provides similar functionality (accent on similar, not identical in all respects).
It would be incorrect to say that MEFedMVVM itself resolves services but MEF does. In my case I use MEFedMVVM and Cinch services and my ViewModel importing constructor looks like:
IMyDataModel modelInterface )
MEFedMVVM creates MyViewModel and MEF takes care of the rest thanks to [ImportingConstructor] attribute and the fact that all the services are MEF-exported (so they can be imported/concrete class instantiated).