OUR TAKE
Message history alongside other macOS services
iMCP is a native macOS app that exposes selected services to MCP clients. Its documented Messages capability reads history, while Calendar, Contacts and Reminders provide other kinds of context and actions.
Choose services one at a time
The app presents services in a menu-bar interface and lets the user activate them individually. This gives a visible place to decide which personal context the assistant can reach.
A permission to read messages should not be bundled casually with calendar or location access. Activate only what the task requires.
Understand the Messages permission path
The README describes a sandboxed app and a file-picker grant for the local chat.db database. Its listed Messages capability is access to participant history within date ranges.
Other app services include write operations, such as creating reminders. Calling this entry read-only refers to its documented Messages scope, not to all actions exposed by the application.
The client receives the result
The project explains that it does not collect or store user data, while connected clients may send tool results off the device. That is an important boundary in the architecture.
Use iMCP when a native service selector and several macOS context sources are useful. Choose a different documented path if the primary requirement is business sending.
The decision in one sentence
Choose iMCP when message history alongside other macos services matches the task and its documented limits fit your client.
Read the primary sources
These are the provider’s own descriptions. Prices and product claims are dated snapshots, and performance claims are not our test results.