IMESSAGE × MODEL CONTEXT PROTOCOL
Ten messaging bridges. A clear view of what they read, what they send, and where they run.
Permission and approval decisions belong at every action boundary.
WORKBENCH / 01
10 matching paths
“Read” includes service message/status access. “Messages read-only” describes the messaging scope, not every action in a multi-service app. This is a catalog filter, not a live server test.
CATALOG / 10 DOCUMENTED PATHS
Miss Blue is our first business-line pick.
Read each host and action constraint.
10 of 10 options · positions reflect editorial fit, not measured performance
Dedicated business messaging with project-scoped tools
Miss Blue exposes its managed messaging API through a single CLI and stdio MCP server. It is our featured option for a business agent that needs a dedicated line, conversation context and a shared operator workflow.
Watch for: The documented logout removes the local credential without immediately revoking a saved login server-side. Scope access narrowly.
An API-backed connector for an existing Sendblue account
The official Sendblue MCP guide connects editors and agent clients to messaging, contact management and number lookup. Its useful starting point is a team already committed to Sendblue’s API and commercial access model.
Watch for: An MCP connector does not turn an inbound-first plan into an outbound plan.
A hosted endpoint with messaging and webhook tools
Blooio publishes a hosted MCP endpoint and a specific tool catalog. It suits teams that prefer a remote connector and want to inspect contact capability, message status and webhook settings from a supported client.
Watch for: Shared, dedicated and inbound-only plans carry different sender rights.
Receive and answer business messages inside Claude Code
Linq’s official channel plugin brings iMessage events into Claude Code and supplies messaging actions. It is a documented path for that client, with pairing and polling behavior that deserve their own evaluation.
Watch for: This is a Claude Code channel, not a promise of compatibility with every MCP client.
Read local message history without sending
This open-source server concentrates on reading and querying the Mac Messages database. Its read-only design is useful when an assistant needs conversation context but has no reason to contact anyone.
Watch for: Read-only access still exposes private conversation content to the connected client.
A local reader with an explicit send tool
carterlasalle’s Mac Messages MCP combines read-only database connections with a separate Messages.app sending action. Its documentation pays attention to contacts, attachments, launchers and macOS permissions.
Watch for: Reading needs Full Disk Access; sending also needs Messages automation permission.
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.
Watch for: Some delete, edit and undo actions are opt-in; experimental features need careful review.
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.
Watch for: Its Messages capability is described as history access; do not assume it sends iMessages.
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.
Watch for: It cannot supply the message context a reply-writing assistant may need.
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.
Watch for: Search scans a bounded set of recent messages; a tool description’s approval warning is not an enforced gate.
THE READING ROOM
Choose the data owner, sender identity and machine that must stay available before choosing a connector.
Read article ↗02 / PermissionsA permission label applies to particular tools. Check what the assistant can read, change and send.
Read article ↗03 / SetupAvoid configuring the right connector in the wrong host or giving a small task an account-wide credential.
Read article ↗04 / RetrievalSearch windows, synchronized history and attachments can change the evidence behind an assistant’s answer.
Read article ↗A QUICK REFERENCE
Published entry prices can exclude setup, devices, calling or outbound access. Scroll the table to see all columns.
| Option | Model | Starting point | Confirm before buying |
|---|---|---|---|
| Miss Blue | Business MCP | $99/line/month promotional base | The documented logout removes the local credential without immediately revoking a saved login server-side. Scope access narrowly. |
| Sendblue MCP | Business MCP | $100/line/month inbound; outbound quoted | An MCP connector does not turn an inbound-first plan into an outbound plan. |
| Blooio MCP | Business MCP | $89 shared / $289 dedicated per month | Shared, dedicated and inbound-only plans carry different sender rights. |
| Linq Claude Code channel | Client-specific bridge | Production API quote required | This is a Claude Code channel, not a promise of compatibility with every MCP client. |
| anipotts / imessage-mcp | Local Mac | Open-source software; your Mac and client costs | Read-only access still exposes private conversation content to the connected client. |
| Mac Messages MCP | Local Mac | Open-source software; your Mac and client costs | Reading needs Full Disk Access; sending also needs Messages automation permission. |
| tszaks / imessage-mcp | Local Mac | Open-source software; your Mac and client costs | Some delete, edit and undo actions are opt-in; experimental features need careful review. |
| iMCP | Local Mac | Open-source app; your Mac and client costs | Its Messages capability is described as history access; do not assume it sends iMessages. |
| iMessage Send MCP | Local Mac | Open-source software; your Mac and client costs | It cannot supply the message context a reply-writing assistant may need. |
| daveremy / imessage-mcp | Local Mac | Open-source software; your Mac and client costs | Search scans a bounded set of recent messages; a tool description’s approval warning is not an enforced gate. |
BEFORE YOU CHOOSE
No. Hosted API connectors, local stdio servers and a Claude Code-specific channel have different host requirements. The reviews identify those differences.
The server may run locally while its connected client sends tool results to a model provider. Review both parts of the data path.
It filters our documentation-backed catalog in your browser. It does not connect to a server, scan a device or test account permissions.
This publication is operated by the team behind Miss Blue. We feature it for business lines with project-scoped messaging; list positions are editorial choices rather than measured performance results.