bluereacher-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUEREACHER_API_KEY | Yes | Your Blue Reacher API key (test keys start with brk_test_, live keys with brk_live_). Required to connect to the Blue Reacher API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_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. |
| get_message_statusA | Look up the delivery status of a queued or sent Blue Reacher message by its id. |
| list_conversationsA | Read recent conversation history for a phone number or group chat over a Blue Reacher line. |
| check_imessage_capabilityA | Check whether phone numbers can receive iMessage vs SMS. Accepts up to 100 numbers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.