OUR TAKE
Read threads and send into an existing conversation
This local Node-based bridge resolves contacts, reads message history and sends through Messages.app. Its documented sending scope is particularly clear: it targets an existing chat rather than creating a new conversation.
Existing chat identity is the boundary
The README describes im_send as targeting an existing conversation by chat identifier and GUID. That is a different workflow from creating a first outbound thread for a new customer.
Resolve the chat and inspect its participants before proposing a message. A contact name alone may be ambiguous across direct and group conversations.
Read the completeness line
The documented search scans up to 5,000 recent messages and returns a coverage line. A summary should preserve that limitation instead of presenting a partial search as the whole archive.
The reader uses local SQLite with attributedBody parsing and optional contact-name resolution. These features depend on the data available on the Mac.
Distinguish a warning from enforcement
The send tool description asks the client to confirm with the user. A textual instruction is useful, but a workflow requiring guaranteed approval should enforce that decision in the client or wrapper.
The README requires Node 22 or later, Full Disk Access for reading and a signed-in Messages app for sending. Bridge Kit has reviewed the documentation, not run this package against private messages.
The decision in one sentence
Choose daveremy / imessage-mcp when read threads and send into an existing conversation 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.