bluereacher-mcp
OfficialEnables sending text and media iMessages to E.164 numbers, checking delivery status, reading conversation history, and verifying whether numbers can receive iMessage versus SMS.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bluereacher-mcp Send an iMessage to +14155552671 saying I'm running late."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
bluereacher-mcp
A Model Context Protocol server for Blue Reacher. It lets an AI agent send iMessage, check delivery status, read conversations, and check iMessage capability over a dedicated line.
Built on the official
@modelcontextprotocol/sdk, stdio transportFour tools:
send_imessage,get_message_status,list_conversations,check_imessage_capabilityReads your API key from the environment
No A2P registration required
Docs: https://docs.bluereacher.com
OpenAPI: https://docs.bluereacher.com/openapi.json
Tools
Tool | What it does |
| Send a text and/or media iMessage to an E.164 number. Paced by default, or instant. |
| Look up delivery status of a queued or sent message. |
| Read recent conversation history for a number or group. |
| Check whether numbers can receive iMessage vs SMS. |
Related MCP server: iMessage MCP Server
Install and run
npm install
npm run build
BLUEREACHER_API_KEY=brk_test_your_key node dist/index.jsA test key (brk_test_...) hits the simulator, so no message is ever sent. Keep live keys (brk_live_...) in the environment, never in a committed config.
Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"bluereacher": {
"command": "npx",
"args": ["-y", "bluereacher-mcp"],
"env": {
"BLUEREACHER_API_KEY": "brk_test_your_key"
}
}
}
}Or point at a local build with "command": "node" and "args": ["/absolute/path/to/dist/index.js"].
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"bluereacher": {
"command": "npx",
"args": ["-y", "bluereacher-mcp"],
"env": {
"BLUEREACHER_API_KEY": "brk_test_your_key"
}
}
}
}Hosted MCP
Blue Reacher also runs a hosted MCP endpoint if you would rather not run this server yourself: https://bluereacher.com/mcp (and a public endpoint at https://api.bluereacher.com/v1/mcp/public). See the docs for details.
Smoke test
Boots the server over an in-memory transport and confirms the tools register. Requires no API key and sends nothing.
npm run smokeLicense
MIT. Copyright 2026 Sagency International LLC (Blue Reacher).
Available Tools
4 toolscheck_imessage_capabilityCheck iMessage capabilityA
Check whether phone numbers can receive iMessage vs SMS. Accepts up to 100 numbers.
Inputs: phones (required).
get_message_statusGet message statusA
Look up the delivery status of a queued or sent Blue Reacher message by its id.
Inputs: message_id (required).
list_conversationsList conversation historyA
Read recent conversation history for a phone number or group chat over a Blue Reacher line.
Inputs: limit, phone, group_chat_id.
send_imessageSend iMessageA
Send a text and/or media iMessage to an E.164 number over a Blue Reacher line. Paced (drip) by default; pass send_mode 'instant' to dispatch now.
Inputs: to (required), message, send_mode, media_urls, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct responsibility: sending, checking delivery status, reading conversation history, and verifying iMessage capability. There is no meaningful overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using snake_case: send_imessage, get_message_status, list_conversations, check_imessage_capability. The naming is predictable and uniform.
Four tools is a reasonable, focused size for an iMessage-sending server. The set feels slightly lean but each tool earns its place and the count is not a problem.
The core iMessage workflow is covered: send, check status, view conversation history, and verify capability. Minor gaps exist, such as no explicit message-content retrieval by ID or inbound message handling, but agents can work around these.
Maintenance
Related MCP Connectors
Real phone numbers for AI agents: SMS, iMessage, WhatsApp, AI voice calls, and inbound events.
Send iMessage, SMS and WhatsApp from a dedicated line, run text campaigns and read replies.
Send and receive iMessage, RCS and SMS from US phone numbers: inbox, contacts, AI agents, lines.
iMessage for AI agents, from your iPhone. No Mac needed, and you choose which chats they read.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, search, and send iMessages with features like contact name resolution, session grouping, and attachment listing. It provides intent-aligned tools to efficiently navigate conversation history and manage messages through natural language queries.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, search, and send iMessages, manage contacts, and access attachments on macOS.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to send and receive iMessages and emails, and manage agent identities, in MCP-compatible clients.618 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables an AI agent to read and send real iMessages—including text, voice notes, stickers, links, images, and reactions—through a managed cloud phone line without needing a Mac.AGPL 3.0