OUR TAKE
A minimal send-only connection
andyjianzhou’s project exposes one send_imessage tool through macOS automation. It is a focused option for a workflow that already knows the recipient and text and does not need to read conversation history.
One action can be enough
The README documents a tool accepting a recipient and message. It uses osascript to interact with Messages rather than opening the history database.
A narrow tool interface makes the proposed send easier to inspect. It does not by itself validate the recipient, consent or accuracy of the message.
No history means no automatic context
The project states it does not need Full Disk Access because it does not read chat.db. Messages automation still operates through the signed-in Mac account.
A client must get conversation context elsewhere if it is expected to answer a recent request. Avoid allowing it to invent missing details simply because a send tool is available.
Put a preview before the action
For this sort of connector, show the exact destination and text before execution. An application can then enforce a user approval decision outside the model’s prose.
It fits occasional, reviewed messages from an owned Mac. It is not a managed business inbox, a webhook service or an independently tested delivery system.
The decision in one sentence
Choose iMessage Send MCP when a minimal send-only connection 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.