Any API module that outputs revision (meta-)data needs to become aware of MCR, and must support multiple content objects per revision in the output.
ApiQueryRevisionsBase and its subclasses need a "slots" parameter, both to select which slots should have content-related metadata returned and to indicate that the existing, main-only content format should no longer be used. A new prop to list the available roles per revision is also useful.