Sendblue MCP Server

An MCP (Model Context Protocol) server that exposes Sendblue's iMessage and SMS capabilities as tools for LLMs.

Local serverstdioPython

What is the Sendblue MCP MCP server?

Sendblue mcp mcp server connects Sendblue MCP to AI assistants that speak the Model Context Protocol. An MCP (Model Context Protocol) server that exposes Sendblue's iMessage and SMS capabilities as tools for LLMs.

What Sendblue MCP does

An MCP (Model Context Protocol) server that exposes Sendblue's iMessage and SMS capabilities as tools for LLMs.

This MCP server acts as an interface to the Sendblue API, enabling LLMs to send messages, manage groups, and perform other communication-related tasks via iMessage and SMS. It follows the MCP specification and provides a standardized way for LLMs to interact with the Sendblue platform.

Key capabilities

  • send_message: Send individual messages (iMessage/SMS) with support for text, media, and expressive styles
  • send_group_message: Send messages to group chats
  • lookup_number_service: Check if a number supports iMessage or SMS
  • send_typing_indicator: Send typing indicators to recipients
  • get_message_history: Retrieve message history
  • add_recipient_to_group: Add new recipients to existing group chats
  • upload_media_for_sending: Upload media from URLs to Sendblue servers

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

Installing the sendblue mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: SENDBLUE_API_KEY_ID, SENDBLUE_API_SECRET_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

  • Python 3.10 or higher - Sendblue API credentials (API Key ID and Secret Key)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Sendblue MCP sits in that group, and the shape of its toolset — Prerequisites, Installation — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by adamanz, written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the sendblue mcp mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
Installation1. Clone this repository: sh git clone https://github.com/your-username/sendblue-mcp.git cd sendblue-mcp

Configuration

  • Python 3.10 or higher - Sendblue API credentials (API Key ID and Secret Key)
VariableDescriptionRequired
SENDBLUE_API_KEY_IDCredential the server authenticates with.Yes
SENDBLUE_API_SECRET_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Sendblue MCP to Prerequisites.
  • Use Sendblue MCP to Installation.

Frequently asked questions

It connects Sendblue MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, Installation) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Sendblue MCP directly.