Bridge KitA workbench for message tools
Menu

Local Mac / SOURCE-BASED REVIEW

iMCP : 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.

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.

iMCP’s Messages scope reads history, while other selected macOS services can have different powers.
iMCP’s Messages scope reads history, while other selected macOS services can have different powers.

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.

This review covers mattt’s native app for macOS 15.3+; unrelated acronym meanings are outside its scope.

Understand the Messages permission path

The picker now requests directory access for Messages, including the write-ahead log. A chat.db-only grant can omit newer entries. Attachment reading requires another optional folder permission.

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.

Sources: Messages code

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.

Investigate a gap before widening access

Begin with a concrete retrieval question: which conversation, which period and which piece of context is needed? A missing recent message is different from an attachment that has not been requested. Keeping those questions separate makes it easier to compare the documented setup with the result you actually need.

Write down the boundary you intend to keep. If the task needs only text history, ask why another service or a file attachment would be necessary before enabling it. The useful outcome is a sufficient answer with an understood data path, not the largest possible collection of enabled services.

For a future check, compare the returned context with an owned conversation whose contents you know. Record gaps and stop a reply workflow when the missing information matters. That is a proposed way to evaluate completeness; no personal Messages database was opened for this review.

Keep retrieval questions distinct
QuestionWhat to clarify
Which project is this?Confirm the repository and app identity
What context is missing?Distinguish recent text from an attachment
Is another permission needed?Tie any change to a specific task

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.