Skip to content
SENDLY by ACTIOSENDLY by ACTIO
Documentation

MCP Server

Send SMS through SENDLY straight from AI agents – Claude Code, Codex CLI, Gemini CLI. Everyone brings their own token, we store nothing.

https://mcp.sendly.link/mcp

How it works

The MCP server acts as a bridge: the agent calls a tool and the server forwards the request to the SENDLY SMS API. It is stateless – you put your SENDLY token in your client config (Authorization: Bearer header) and the server forwards it 1:1 to api.sendly.link, storing nothing. Everyone sends from their own account.

Client setup

Paste your SENDLY token into your MCP client config. Ready-made entries for the most popular tools below.

{
  "mcpServers": {
    "sendly": {
      "type": "http",
      "url": "https://mcp.sendly.link/mcp",
      "headers": { "Authorization": "Bearer TWOJ_TOKEN_SENDLY" }
    }
  }
}

Or with a single command (Claude Code)

claude mcp add --transport http sendly \
  https://mcp.sendly.link/mcp \
  --header "Authorization: Bearer TWOJ_TOKEN_SENDLY"

Tools

The server exposes one tool – sending a single SMS.

send_sms
  • tostringrequired

    Destination Polish mobile number, 9–11 digits (e.g. 48732129001).

  • bodystringrequired

    Message content. UCS-2 encoding, split into segments every 60 characters.

  • fromstring

    Optional sender number (a SENDLY virtual number), 9–11 digits.

Limits and security

  • The token is never stored or logged – it lives only in the request header.
  • Rate limit: 10 SMS/60 s per token + 60 requests/60 s per IP.
  • Hard daily cap: 200 SMS per token.
  • Max message length: 2000 characters (longer messages split into multiple SMS segments).
Create an account and get a tokenAPI Reference (REST)