Official Sendblue connector for sending and reading customer messages from MCP-compatible AI assistants over iMessage, RCS, and SMS.
Connect
Add a remote HTTP MCP server in your assistant using:
https://api.sendblue.co/mcp
Choose OAuth sign-in, sign in to your Sendblue account, select your workspace, and approve the requested access. The server supports OAuth 2.1 with PKCE and dynamic client registration. Do not put API keys or account passwords into the server URL or configuration.
{
"mcpServers": {
"sendblue": {
"type": "http",
"url": "https://api.sendblue.co/mcp"
}
}
}
Use a client that supports remote HTTP MCP and OAuth. Exact configuration syntax can vary by client.
Tools
| Tool | What it does |
|---|
ping | Checks connectivity to the authenticated workspace. |
list_lines | Lists the workspace's sending lines. |
list_messages | Reads recent messages and replies. |
send_message | Sends a one-to-one text message through Sendblue. |
get_message_status | Checks a message's delivery status. |
evaluate_service | Produces a bounded messaging-health summary for the workspace. |
Try it
- "List my Sendblue sending lines."
- "Show my recent Sendblue messages."
- "Send [message] to [opted-in recipient] from [my sending line]."
- "Check the delivery status of [message handle]."
Confirm the recipient, message, and sending line before sending. An accepted or queued message is not yet proof of delivery; check its status before retrying.
Account requirements
A Sendblue account is required. The connector also works with a free Sendblue account, subject to that plan's limits. Free shared-line accounts must verify recipients before sending. Messaging limits and account permissions continue to apply.
Links
Support: support@sendblue.com
Comments