OUR TAKE
A broad local toolkit for messages and attachments
This project documents local history access, attachment retrieval, sending and optional mutation features. Its appeal is breadth, particularly when the assistant needs to inspect media alongside the thread.
Media expands the assistant’s context
The README describes returning image attachments as content blocks, converting HEIC images and returning metadata or paths for other files. That can help a multimodal task, but it also expands the customer data given to the client.
Check the exact attachment chosen and whether the connected model receives it. Start with an owned test image rather than a large private conversation archive.
Review release flags before enabling them
Optional flags expose fallback, local cleanup and experimental Messages UI actions. The repository describes different confirmation behavior for individual message deletion and full-thread deletion.
Do not treat every mutation as protected by the same approval step. Leave unneeded actions disabled and read the current tool behavior before adding them to an assistant.
Match the runtime to the repository
The fetched README requires Node 18 or later but below 26, recommending Node 24 because of the native SQLite dependency. It also requires macOS and Full Disk Access.
This is a documented requirement snapshot, not an installation test performed by Bridge Kit. Verify compatibility on the exact Mac and client you plan to use.
The decision in one sentence
Choose tszaks / imessage-mcp when a broad local toolkit for messages and attachments 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.