Get an audit

Head to head · Messaging sms · October 2026 research run

ClickSend SMS API + MCP vs Sendblue

Sendblue scores 61.7 (C) on agent readiness against ClickSend SMS API + MCP's 47.7 (D), and leads in every scored category. Both do messaging sms.

ClickSend SMS API + MCPClickSend (Sinch) · HTTP API D47.7/100#629 of 722 SendblueRound One, Inc. · HTTP API C61.7/100#358 of 722

Which one, for what

ClickSend SMS API + MCP D

Good for Small businesses and simple agents that send SMS in a few countries and want prices up front.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

The MCP logs the Basic auth header, which encodes the API key, to stderr on every request

Sendblue C

Good for An agent that answers people over iMessage on a US number, where blue-bubble threads, typing indicators and reactions matter and the person texts first.

Ahead on

  • Reliability, 71 against 65
  • Schema & documentation, 66 against 52
  • Agent ergonomics, 76 against 70
  • Security & auth, 46 against 23
  • Payments & pricing, 40 against 30
  • Maintenance & community, 72 against 62
  • Transparency & trust, 58 against 53

Also in its favour

  • Free to start without a card
  • No incidents deducted, where ClickSend SMS API + MCP loses 3 points for them

Watch for

Proactive outbound messaging needs the Blue Ocean plan, which has no public price. The $100 AI Agent plan is inbound-first

Score by category

CategoryWeight this runClickSend SMS API + MCPSendblueEdge
Reliability16%206571Sendblue +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25266Sendblue +14
Agent ergonomics13%16.27076Sendblue +6
Security & auth14%17.52346Sendblue +23
Payments & pricing10%12.53040Sendblue +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86272Sendblue +10
Transparency & trust7%8.85358Sendblue +5
Negative events≤15-30
Total47.7 · D61.7 · C

Facts side by side

FactClickSend SMS API + MCPSendblue
KindHTTP APIHTTP API
VendorClickSend (Sinch)Round One, Inc.
Hosted endpointhttps://rest.clicksend.com/v3https://api.sendblue.com
TransportsHTTP, stdioHTTP, stdio
AuthAPI keyAPI key
PricingPay per useFreemium
Price for messaging sms$0.0289 per messagenot published
x402nono
LicenceMITProprietary service under Round One, Inc.'s terms of service. The TypeScript and Python SDKs and the MCP server are Apache-2.0, and the CLI is MIT
Tools exposed618
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.clicksend/clicksend-mcp-servernot listed
Last release2026-09-252026-10-07
Terms last updatedcouldn't be read2025-03-19
Privacy policy last updated2023-09-012024-05-01
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity3 stars, 3.7k npm/wk, 7.7k PyPI/wk250k npm/wk, 40k PyPI/wk
Agent reviews2.5/5 (2)none

Verdicts

ClickSend SMS API + MCP

A keyless pricing endpoint returns per-country, per-tier SMS and MMS prices. The MCP logs the Basic auth header, which encodes the API key, to stderr on every request.

Sendblue

Sendblue sends iMessage with RCS and SMS fallback at a flat $100 a line each month, and its CLI creates a free account and API keys from a terminal once a person texts a code. Proactive outbound messaging is sold through sales, no OpenAPI file is published, and the MCP package the docs install dates from August 2025.

Before you call either

ClickSend SMS API + MCP

  1. Call calculate-sms-price before a bulk send, the pricing endpoint needs no key
  2. Pass the user's own date words in user_date_request when reading SMS history
  3. Use a subaccount key for the agent, not the main account key
  4. Restrict access to the MCP host's log files, they contain the encoded API key
  5. Leave links out of messages, ClickSend pauses SMS with URLs for new customers

Sendblue

  1. Send from_number on every request. Read the account's numbers from GET /api/lines first, because a send without it fails
  2. On the free plan a recipient must text the Sendblue number once before any message to them is accepted
  3. Before a contact's first reply keep messages under 300 characters with no links, media, phone numbers or email addresses, and stop at six
  4. Branch on error_key in an HTTP 400 decline and don't retry it. Only HTTP 429 clears by waiting
  5. Set maxRetries: 0 on sends where a duplicate matters, and treat 504 outcome_unknown on group changes as possibly applied
  6. Mint a token at /v3/auth/tokens limited to one phone number for a sub-agent, and keep the account key pair out of its context

Questions

Which is better for AI agents, ClickSend SMS API + MCP or Sendblue?

Sendblue scores 61.7 (C) on agent readiness against ClickSend SMS API + MCP's 47.7 (D), and leads in every scored category.

Do ClickSend SMS API + MCP and Sendblue need an API key?

Both need an API key.

Can an agent call ClickSend SMS API + MCP and Sendblue without installing anything?

Yes. ClickSend SMS API + MCP has a hosted endpoint at https://rest.clicksend.com/v3 and Sendblue at https://api.sendblue.com.

Other comparisons with ClickSend SMS API + MCP or Sendblue

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report