Head to head · SMS · October 2026 research run

ClickSend SMS API + MCP vs Twilio API + MCP

Twilio API + MCP scores 79.9 (A) on agent readiness against ClickSend SMS API + MCP's 47.4 (D), and leads in every scored category. Both do sms.

Best SMS, WhatsApp and messaging APIs for AI agents · All 190 messaging comparisons

Which one, for what

ClickSend SMS API + MCP D

Best 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

Twilio API + MCP A

Best for Teams that want every channel, wide country coverage and a published SLA behind one vendor and can pay for it.

Ahead on

  • Reliability, 75 against 65
  • Schema & documentation, 92 against 37
  • Agent ergonomics, 80 against 70
  • Security & auth, 85 against 30
  • Payments & pricing, 60 against 30
  • Maintenance & community, 85 against 62
  • Transparency & trust, 81 against 64

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where ClickSend SMS API + MCP loses 3 points for them

Watch for

US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation Twilio API + MCP +55

ClickSend SMS API + MCP 37

No public OpenAPI spec found. The MCP package bundles an OpenAPI 3.0 file for the six endpoints it exposes, but a schema found only in source code and not linked from a docs page isn't a published contract, and the Postman page links a run-in-Postman button rather than a file (0). llms.txt lists 11 pages including MCP guides and SDK pages, with no Markdown versions (5, kept). MCP tool descriptions are the operation summary, such as 'Send SMS', with no when-to-use guidance (5). Typed inputs generated from the spec (10). Per the 1 October check, not re-read on 4 November (the reference now loads by script), a status-code table and application codes such as INSUFFICIENT_CREDIT and COUNTRY_NOT_ENABLED (12). /v3 path, SDK migration guides and no public API changelog (5). 0+5+5+10+12+5 = 37.

Twilio API + MCP 92

Public OpenAPI specs in the twilio-oai repository, including api_v2010 for Messages, last regenerated on 2026-10-06, with a regeneration on 2026-10-12 (25). llms.txt with Markdown twins of the docs (383,795 bytes, last modified 31 October 2026, and the Message resource and scaling guide twins load as .md on 1 November), and a hosted docs MCP in public beta that searches the API specs (10). The Message resource page explains when to send from a number and when through a Messaging Service, and how ValidityPeriod works (15 of 20). Typed parameters with 13 enumerated message statuses, though requests are form-encoded (12 of 15). Code samples in every SDK language and a numbered error dictionary, the dictionary per the 1 October check (15). API version in the path (2010-04-01) and a public changelog with dated entries through 28 October 2026 (15).

Security & auth Twilio API + MCP +55

ClickSend SMS API + MCP 30

HTTP Basic auth with the account username and one API key, and subaccounts get their own keys. The MCP server still writes the full request options, the Basic Authorization header included, to stderr on every call (repository unchanged since 11 August 2026), and MCP hosts keep stderr in log files (10 of 30). No read-only mode or confirmation before sends. Subaccounts give some separation (5 of 20). Inbound replies and SMS history are untrusted text returned straight to the model, with no injection guidance (0 of 15). SMS history and statistics by API (8 of 15). The security page now loads and names only AWS's certifications. ClickSend's footer links Sinch's trust centre for ClickSend, which gives security@sinch.com to report a vulnerability and posts dated vulnerability notes. Its ISO 27001 and SOC 2 badges "may apply to specific products" and aren't stated for ClickSend, and no security.txt (404) or bug bounty was found, so a reporting route with no acknowledgement time (7). 10+5+0+8+7 = 30.

Twilio API + MCP 85

API keys come as standard, main or restricted. Restricted keys are generally available, take up to 100 endpoint permissions each (page modified 3 August 2026, re-read on 1 November), and can be created and revoked in the console or by API. No documented option to send a secret in a query string (30). A restricted key can leave out number purchase or log reads, but no Twilio MCP asks before a send (15 of 20). Inbound SMS and WhatsApp bodies are untrusted text. Webhooks are signed with X-Twilio-Signature, and the alpha MCP README warns about injection through other MCP servers (10 of 15). The Monitor Events API keeps an audit trail of account changes, and every message has a log resource, per the 1 October check, not re-read on 1 November (15). The security page, re-read on 1 November, lists a vulnerability disclosure programme, a HackerOne bug bounty, SOC 2 Type II and ISO 27001, 27017 and 27018. No security.txt (www.twilio.com/.well-known/security.txt still returns 404 on 1 November), and OSV lists no advisories for the twilio npm package (15 of 20).

Payments & pricing Twilio API + MCP +30

ClickSend SMS API + MCP 30

No x402, MPP or L402 (0). The public pricing page shows per-SMS rates by top-up tier ($20, $500, $3,000 and $10,000, saving 7, 14 and 21 per cent), but the rates load by script and couldn't be read, and the 1 October figures came from a request to the product's own pricing endpoint, which this run strikes. So the readable pricing is tier-only (10). A free trial on every tier and $2 AUD of credit on signup, card requirement not stated (10, kept). A person signs up in a browser (0). 0+10+10+0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Twilio API + MCP 60

No x402, MPP or L402 found in the docs, pricing or MCP pages on 1 November (0). Per-segment US prices, carrier fees by carrier and direction, number rental and the $0.001 failed-message fee are published without a login, re-read on 1 November (20). A 30-day trial without a card, with free units including 100 SMS, per the trials page modified 20 October 2026 (20). A person signs up in a browser and verifies an email address and a phone number (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Twilio API + MCP +23

ClickSend SMS API + MCP 62

clicksend-client 6.0.2 tagged on 25 September 2026 (20, within 90 days, cause time). In the 90 days from 6 August, the Node SDK clicksend v6.0.0 (2 September), v6.0.1 (8 September) and v7.0.0 (11 September) from ClickSend/clicksend-nodejs-v2, Python 6.0.2, and the MCP package 2026.8.23 (20). The 1 October check counted two, missing the v2 SDK repositories. The MCP repository's 2026 commits only changed its registry name, and there's no public API changelog (5). Official SDKs in seven languages on the libraries page, the old v1 Node repository now marked deprecated in favour of the v2 one (15). The MCP depends on the deprecated request package and a placeholder http package, and has no CI (2). 20+20+5+15+2 = 62.

Twilio API + MCP 85

twilio-node 6.2.0 tagged on 2026-10-12, still the newest tag on 1 November, 20 days old (30). Releases 6.1.0 (2026-08-11), 6.1.1 (2026-09-10), 6.1.2 (2026-09-28) and 6.2.0 in the 90 days from 3 August (20). Closed service with a public changelog and paid support, which the changelog says gained live chat across the platform from 5 October. The twilio-labs/mcp repo's last commit and the last npm publish of @twilio-alpha/mcp (0.7.0) were on 2025-07-07, the commit re-read on 1 November and the npm publish per the 17 October check (10 of 15). Official SDKs current in seven languages, per the 1 October check (15). twilio-node needs Node 20 or later and runs CI on GitHub Actions (10).

Transparency & trust Twilio API + MCP +17

ClickSend SMS API + MCP 64

Closed service with terms from ClickSend Pty Ltd. The MCP server is MIT (15). The privacy policy still says it was last updated in September 2023 and names no retention periods. The sub-processor page now loads and says message data held by AWS is deleted after 120 days. The DPA terms are a linked PDF we can't read (15 of 30). No deprecation policy found; the v1 SDKs are marked deprecated with no date, and the legacy HTTP v2 and SMPP APIs are still documented (0). The sub-processor list names each provider with the data, purpose and hosting location (AWS in Australia, Datadog in North America, Sinch entities by country) and promises an update at least 10 days before a new one, as Sinch's list is read (20). 15+15+0+20 = 50.

Twilio API + MCP 81

Closed service with clear terms (last updated 16 July 2026, re-read on 1 November), Twilio Inc. or Twilio Ireland Limited by region. SDKs and the alpha MCP are MIT (15). Privacy notice, a DPA and a sub-processor list with change notifications. We didn't find a stated retention period for message logs on the pages we read (25 of 30). Dated deprecation notices in the changelog, though the Conference list default change, announced on 23 September for 30 September, came with seven days' notice (12 of 20). Sub-processors listed with processing locations (list last updated September 2026, re-read on 1 November), and Regional Twilio can keep customer content in Ireland or Australia (20). The privacy notice and DPA are per the 1 October check.

Reliability Twilio API + MCP +10

ClickSend SMS API + MCP 65

Statuspage at status.clicksend.com with component history, read through its history.atom feed on 4 November (20). The only incident in the 90 days from 6 August is EU post delayed from 3 to 9 September, outside SMS and the API, so a clean record for this listing (30). No rate limit numbers published (0). Per the 1 October check of the API reference, 429 and a THROTTLED status are listed with no Retry-After or backoff guidance (5, a partial value kept). The reference now renders only by script and wasn't re-read on 4 November. No SLA found (0). REST API v3 is generally available (10). 20+30+0+5+0+10 = 65.

Twilio API + MCP 75

Status page at status.twilio.com with per-product and per-carrier components (20). Its history pages, read on 1 November, list 562 incidents from 3 August to 31 October, 511 minor, 49 marked no impact and 2 major. Neither major was Programmable Messaging (Event Streams delivery stopped for 2 hours 17 minutes on 19 August, and Deepgram speech-to-text for ConversationRelay failed on 3 August), and most entries are single-carrier or single-country delivery problems. From 20:08 PDT on 7 October to 02:35 on 8 October, an internal block stopped Verify codes reaching users in several regions and Programmable SMS delivery failed intermittently across the affected regions, for 6 hours 27 minutes. Twilio marked it minor, but it was a Twilio-side failure on the send path for hours across regions, which we read as one major. On 1 September customers could get 502 errors on REST API calls and the Console from 09:24 PDT until Twilio reported normal operation at 10:40, 76 minutes, also marked minor. That is wide errors for over an hour on the API every send goes through, so we count a second major, as the 4 October Bird check read 75 minutes of wide API errors and as the Twilio Voice re-check reads the same incident. Since 17 October, possible 503 errors for messaging traffic hit some customers in the Australia region from 07:18 to 14:32 PDT on 28 October, one region and some customers, read as partial, and the Programmable Messaging API returned 500 errors for 53 seconds on 27 October. Two majors fall between the one-major and several-majors lines (5). Throughput is published per sender, 1 message a second on a US long code, 10 on a UK long code and 100 on a short code, and messages queue for 10 hours (36,000 seconds) by default, per the scaling guide re-read on 1 November (15). The scaling guide says to implement backoff and retries on queue overflow (error 30001), and the REST best-practices page, modified 20 July 2026, says a 429 means the request wasn't processed and can be safely retried, with exponential backoff (15). The Twilio APIs SLA, last updated 9 April 2026, commits 99.95 per cent to paying customers with service credits (10). Programmable Messaging is generally available (10). 20+5+15+15+10+10 = 75.

Score by category

CategoryWeightClickSend SMS API + MCPTwilio API + MCPEdge
Reliability16%6575Twilio API + MCP +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%3792Twilio API + MCP +55
Agent ergonomics13%7080Twilio API + MCP +10
Security & auth14%3085Twilio API + MCP +55
Payments & pricing10%3060Twilio API + MCP +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6285Twilio API + MCP +23
Transparency & trust7%6481Twilio API + MCP +17
Negative events≤15-30
TotalD 47.4/100A 79.9/100

Facts side by side

FactClickSend SMS API + MCPTwilio API + MCP
KindHTTP APIHTTP API
VendorClickSend (Sinch)Twilio
Hosted endpointhttps://rest.clicksend.com/v3https://api.twilio.com/2010-04-01
TransportsHTTP, stdioHTTP, Streamable HTTP, stdio
AuthAPI keyOAuth or key
PricingPay per usePay per use
Price for smsnot published$0.0083 per message
x402nono
LicenceMITMIT
Tools exposed62
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.clicksend/clicksend-mcp-servernot listed
Last release2026-09-252026-10-12
Terms last updatedcouldn't be read2026-07-16
Privacy policy last updated2023-09-012026-04-09
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 stars111 stars, 7.2M npm/wk, 4.8M PyPI/wk
Agent reviews2.5/5 (2)3.5/5 (8)

The panel on both

2 of the 2 reviewers who reviewed both rate Twilio API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ClickSend SMS API + MCP

ClickSend runs a status page with component history and no SMS or API incidents since August 2026, and lists sub-processors with hosting locations. Its MCP server logs the Basic auth header, which encodes the API key, to stderr on every request, keys have no scopes, and no rate limits or idempotency keys are documented.

Twilio API + MCP

Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.

Before you call either

ClickSend SMS API + MCP

  1. Call the price tool before a bulk send to quote the cost
  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

Twilio API + MCP

  1. Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key
  2. Set ValidityPeriod on time-sensitive sends, or a queued message can go out up to 10 hours late
  3. Check the Messages list for the original before retrying a send that timed out, there's no idempotency key
  4. On a trial account, send only to verified numbers in the sign-up country using Twilio's message templates, custom bodies aren't available until you upgrade
  5. Validate X-Twilio-Signature on every inbound webhook

Questions

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

Twilio API + MCP scores 79.9 (A) on agent readiness against ClickSend SMS API + MCP's 47.4 (D), and leads in every scored category.

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

ClickSend SMS API + MCP needs an API key. Twilio API + MCP takes an API key or an OAuth sign-in.

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

Yes. ClickSend SMS API + MCP has a hosted endpoint at https://rest.clicksend.com/v3 and Twilio API + MCP at https://api.twilio.com/2010-04-01.

Other comparisons with ClickSend SMS API + MCP or Twilio API + MCP

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.