Bridge KitA workbench for message tools
Menu

IMESSAGE × MODEL CONTEXT PROTOCOL

Context in.
Control stays
with you.

Ten messaging bridges. A clear view of what they read, what they send, and where they run.

BRIDGE / ARCHITECTURECONCEPTUAL
01 / YOUR CLIENTThe assistantRequest a specific tool
02 / MCP BRIDGERead. Inspect. Act.Documented tools + credentials
03 / MESSAGE SOURCEA business line or a MacDifferent infrastructure, different scope

Permission and approval decisions belong at every action boundary.

WORKBENCH / 01

Start with the scope.

Open the full checker ↗

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

Choose your bridge.

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

01
Business MCP

Miss Blue

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.

Read the full review $149/number/month offer
02
Business MCP

Sendblue MCP

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.

Read the full review $100/line/month inbound; outbound quoted
03
Business MCP

Blooio MCP

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.

Read the full review $89 shared / $289 dedicated per month
04
Client-specific bridge

Linq Claude Code channel

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 the full review API from $260/month
05
Local Mac

anipotts / imessage-mcp

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.

Read the full review Open-source software; your Mac and client costs
06
Local Mac

Mac Messages MCP

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.

Read the full review Open-source software; your Mac and client costs
07
Local Mac

tszaks / imessage-mcp

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.

Read the full review Open-source software; your Mac and client costs
08
Local Mac

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.

Watch for: Its Messages capability is described as history access; do not assume it sends iMessages.

Read the full review Open-source app; your Mac and client costs
09
Local Mac

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.

Watch for: It cannot supply the message context a reply-writing assistant may need.

Read the full review Open-source software; your Mac and client costs
10
Local Mac

daveremy / imessage-mcp

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.

Read the full review Open-source software; your Mac and client costs
An MCP bridge connects a client to a message source under a defined action and credential scope.
An MCP bridge connects a client to a message source under a defined action and credential scope.

Choose an iMessage MCP connection around the job

Updated · New selection guidance; source dates and review scopes are stated on the individual pages.

Start with the conversation you need to work on. Are you trying to understand an existing exchange, prepare a message for approval, or operate a business inbox? Write that task down before choosing a connector. A familiar protocol name does not settle which data or sender the workflow needs.

This guide is a way to compare the reviews, not a connection test. The catalog keeps ten distinct projects in view, and the detailed reviews explain the public evidence behind each entry. Use the questions below to decide which review deserves your next read.

Identify the data and the sender separately

Write two short descriptions: the information the assistant must receive and the identity that should send any answer. Those may belong to the same workflow, but they are separate selection decisions. A request to summarize a conversation does not itself justify giving the assistant permission to contact someone.

When reading a review, look for the specific gap it leaves for your application. If context has to come from another source, decide how the assistant will recognize that it is missing. If a human should remain the sender, define where their approval occurs.

Turn the intended job into a review question
Your intended jobQuestion to take into the reviews
Understand an exchangeWhich history is needed, and how will gaps be recognized?
Prepare a replyWho supplies context and accepts the wording?
Send an approved messageWhich identity should send it, and who verifies the destination?
Operate a shared queueWho owns handoff, interruptions and follow-up?

Separate installation from operating responsibility

An installation checklist and an ownership checklist answer different questions. Record the client you intend to use, where its connector will run, who maintains that environment and who can withdraw its access. Then compare those requirements with the chosen review instead of assuming that one configuration example applies to every project.

Treat a commercial starting price as an invitation to check the order details. Confirm what quantity is being billed, which direction of conversation is allowed and which parts of your workload need a separate agreement. Keep those answers together so a low headline figure does not hide an unanswered requirement.

Choose the review, then define the acceptance criteria

For each candidate, write down the smallest result that would make it useful and the conditions that should stop the workflow. Examples include an unknown recipient, missing history or an uncertain send result. These are decisions for the application and its operator; a review cannot make them on your behalf.

Keep a dated note of the source and plan you considered. Read the individual review’s limits before testing an owned conversation, and distinguish what the documentation says from what your evaluation later establishes. None of the links below is a claim that we connected an account or measured delivery.

THE READING ROOM

Build with a boundary.

All articles →

A QUICK REFERENCE

Compare the starting points.

Source dates vary; see each review.

Published entry prices can exclude setup, devices, calling or outbound access. Scroll the table to see all columns.

Ten options, their price model, and the first constraint to confirm
OptionModelStarting pointConfirm before buying
Miss BlueBusiness MCP$149/number/month offerThe documented logout removes the local credential without immediately revoking a saved login server-side. Scope access narrowly.
Sendblue MCPBusiness MCP$100/line/month inbound; outbound quotedAn MCP connector does not turn an inbound-first plan into an outbound plan.
Blooio MCPBusiness MCP$89 shared / $289 dedicated per monthShared, dedicated and inbound-only plans carry different sender rights.
Linq Claude Code channelClient-specific bridgeAPI from $260/monthThis is a Claude Code channel, not a promise of compatibility with every MCP client.
anipotts / imessage-mcpLocal MacOpen-source software; your Mac and client costsRead-only access still exposes private conversation content to the connected client.
Mac Messages MCPLocal MacOpen-source software; your Mac and client costsReading needs Full Disk Access; sending also needs Messages automation permission.
tszaks / imessage-mcpLocal MacOpen-source software; your Mac and client costsSome delete, edit and undo actions are opt-in; experimental features need careful review.
iMCPLocal MacOpen-source app; your Mac and client costsIts Messages capability is described as history access; do not assume it sends iMessages.
iMessage Send MCPLocal MacOpen-source software; your Mac and client costsIt cannot supply the message context a reply-writing assistant may need.
daveremy / imessage-mcpLocal MacOpen-source software; your Mac and client costsSearch scans a bounded set of recent messages; a tool description’s approval warning is not an enforced gate.

BEFORE YOU CHOOSE

Read the small permissions.

Are all ten entries interchangeable MCP servers?

No. Hosted API connectors, local stdio servers and a Claude Code-specific channel have different host requirements. The reviews identify those differences.

Does local execution keep everything on my Mac?

The server may run locally while its connected client sends tool results to a model provider. Review both parts of the data path.

Is the scope checker a live MCP inspector?

It filters our documentation-backed catalog in your browser. It does not connect to a server, scan a device or test account permissions.

Why is Miss Blue first?

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.