Bridge KitA workbench for message tools
Menu

Local Mac / SOURCE-BASED REVIEW

iMessage Send MCP : 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.

By Bridge Kit editorial · Published · Updated

This update revises the setup and decision guidance below. It is based on public documents, not a connected-account test.

Repository files retrieved November 9, 2026; the repository head was unchanged when checked November 10. Original publication and earlier source records are retained.

iMessage Send MCP is a narrow send-only path and does not provide the missing thread context.
iMessage Send MCP is a narrow send-only path and does not provide the missing thread context.

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.

The documented prerequisites include Python 3.11+ and an open, signed-in Messages app.

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.

The launcher names a Python module, not a universal iMessage executable. Match the configured interpreter to the installation being used.

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 inspected handler has no approval branch. A successful automation return is not independent delivery confirmation.

Sources: Handler code

Define what a successful send means

A send-only task starts after the destination and wording have been settled. If the assistant is expected to answer a customer, specify where the missing conversation context will come from before offering it a sending action. A concise tool interface does not repair an incomplete brief.

Separate the decision to attempt a send from the evidence used to judge its outcome. Decide what the application will record, what uncertainty it will show to a person and when it will stop instead of trying again. Automatic repetition can be the wrong response when the previous outcome is unclear.

For setup questions, identify the project and the client configuration first. An executable path copied from a different tool or machine can describe a different installation entirely. This review does not diagnose a particular Mac; use the linked project documentation alongside the configuration you actually control.

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.