Sendblue

Evaluate the health of this Sendblue account's recent outbound messaging: status populations, transport-error and confirmed-delivery rates, and recent failure reasons. Always reports over an explicit time window (default the last 24 hours) and samples at most the newest 100 messages in it — check total_in_window and sampled before treating the counts as complete. Every rate is reported next to the denominator it came from: completed_attempts excludes declined messages (rejected before transport) and in-flight ones (not finished). confirmed_delivery_rate_pct counts only messages with a delivery receipt, and SMS produces no receipts — SMS-heavy traffic therefore shows a low rate while still delivering, so read it alongside by_service. This is not the same metric as the dashboard analytics delivery rate, which uses a different denominator; the two numbers are not expected to match.

Get message delivery status by UUID. Read access includes message details; send-only access returns only the status of a send made by this connected app.

List all Sendblue phone numbers assigned to the authenticated account.

List messages for the authenticated Sendblue account, newest first.

Echo back a message. Use this to verify the MCP connection is working.

Send an iMessage or SMS to a phone number on behalf of the authenticated Sendblue account. This sends a real message. Use a new UUID idempotency_key for each intentional message and reuse it with identical inputs for every retry. If the outcome is unknown, check the returned UUID with get_message_status; do not retry using a new key. Accounts on the free plan send from a shared Sendblue line: they must pass from_number, and they can only message contacts whose routing has already been established — the contact was added in the Sendblue dashboard and has since replied to the shared line. These tools cannot create or verify that routing state, so sending to a contact that lacks it fails with "This contact must be verified before sending messages to it."