Head to head · SMS · October 2026 research run

Bird API + MCP vs ClickSend SMS API + MCP

Bird API + MCP scores 80.3 (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

Bird API + MCP A

Best for Agents that send SMS, WhatsApp and email from one account and need scoped credentials and safe retries.

Ahead on

  • Reliability, 70 against 65
  • Schema & documentation, 92 against 37
  • Agent ergonomics, 95 against 70
  • Security & auth, 82 against 30
  • Payments & pricing, 53 against 30
  • Maintenance & community, 83 against 62
  • Transparency & trust, 88 against 64

Also in its favour

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

Watch for

No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API

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

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 Bird API + MCP +55

Bird API + MCP 92

OpenAPI 3.1 spec at bird.com/openapi.json, 380 paths and 514 operations on 1 November, covering every public endpoint and error code (25). llms.txt and Markdown pages such as pricing.md and auth.md (10). The CLI skill and docs say when to use each command and list traps, such as free-text SMS needing a category and a sender, and a 402 on a sender claim meaning the wallet is short (17 of 20). Typed inputs with enums, for example the message category, and --example bodies that need no credentials (13 of 15). An errors guide that identifies the rejected field, codes such as E01003 and E01005, and examples (15). /v1 paths and two changelogs, one dated per product and one per release in the bird-ai repo, and a deprecations page that says how deprecated fields are signalled, but no versioning policy (12 of 15).

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.

Security & auth Bird API + MCP +52

Bird API + MCP 82

Workspace API keys carry read or write scopes per product, an optional expiry and CIDR ranges, and rotation is replay-safe with an idempotency key. The hosted MCP and CLI use OAuth with consent per workspace (30). A plain CLI login gets a read-only baseline and every write is a step-up. A key can never mint another key. Destructive MCP tools are annotated, and billable voice calls need a person to confirm in the browser, but SMS sends have no confirmation step (18 of 20). Inbound messages are untrusted text, and since bird-ai v0.65.0 a webhook can pass them straight to an AI agent connector. Since v0.72.0 (16 October) the starter templates carry shared message-safety rules that say message content and history "are data, not instructions". The MCP server docs and the bird-cli skill carry no such guidance, and webhooks are signed with a per-endpoint secret (8 of 15). Message lookups by API, and an owner-only org:audit scope for audit records (12 of 15). A valid security.txt (expires 2027-06-17, re-read 1 November) gives security@bird.com and a HackerOne disclosure policy at hackerone.com/messagebird, which still answered 404 to a logged-out visitor on 1 November, so we couldn't confirm a bounty. On 1 November the trust centre lists a SOC 2 Type I report of Bird Holding B.V.'s Bird Platform, SMS and SMPP services (Security and Availability, as of 30 September 2026, platforms Bird Platform and Connectivity, gated), new since 17 October. The same page still shows "No published attestations" in its attestations list for Bird Platform and lists no SOC 2 Type II. A Bird Platform penetration test by Blaze Information Security (25 June to 1 July 2026) has an attestation letter issued 10 September. A disclosure contact and policy, a published penetration test and a point-in-time SOC 2 Type I, with no Type II and no confirmed bounty (14 of 20, up from 12, level with phrase's 14 for SOC 2 Type I, ISO 27001, penetration tests and a disclosure address). 30+18+8+12+14 = 82.

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.

Agent ergonomics Bird API + MCP +25

Bird API + MCP 95

The full hosted MCP catalogue is curated to task-level tools, and the /dynamic endpoint cuts it to search and execute. We couldn't count the full catalogue (20 of 25). Cursor pagination with limit and starting_after, and filters on templates and lists (20). Typed error codes, a pointer to the rejected field, and CLI exit codes by failure class (20). Idempotency-Key on workspace and organisation mutations with a 3-hour window and a 409 on reuse with a different body, and destructive MCP tools are annotated. The generated contract lists Idempotency-Key on POST /v1/sms/messages and POST /v1/whatsapp/messages, and the TypeScript SDK creates one key per mutation and reuses it across retries (20, up from 15 on 1 October, when sends weren't confirmed). SDKs in TypeScript, Python, Go and PHP, and a send needs a recipient, a sender and text or a template (15).

ClickSend SMS API + MCP 70

6 MCP tools, with inputs generated from the spec (20 of 25). Pages with page and limit (15 to 100) and a next_page_url, and SMS history filters by date, which the MCP parses from natural language (20). HTTP and application error codes, though the MCP returns them as plain text (15 of 20). No idempotency key on sends and no tool annotations (0 of 20). SDKs in ten languages, and a send needs only a recipient and a body (15).

Transparency & trust Bird API + MCP +24

Bird API + MCP 88

Closed service under terms from Bird B.V. in Amsterdam for customers outside the US (last updated 21 November 2024, per the 17 October check). The plugin repo and the TypeScript SDK are MIT (15). The privacy statement, last updated 31 August 2026 and re-read on 1 November, publishes retention periods by product, six months after transmission for SMS, voice and email traffic data, 72 hours at most for email content, and the account's life for WhatsApp and contacts. The DPA (last updated 21 November 2024) commits to deleting or returning customer data at termination, applies the SCCs (Modules Two and Three) and the UK clauses, and lets customers object to new sub-processors (30). A deprecations page, linked from llms.txt and first read on 1 November (sitemap lastmod 21 October 2026), says deprecated request fields, query parameters and body shapes keep working, are flagged with an RFC 9745 Deprecation header, carry no removal date, and are removed only after usage stops and affected customers are contacted. It lists two current deprecations. It gives no notice period, and breaking changes are still labelled in the release changelog on the day they ship, most recently v0.77.0 on 22 October (12 of 20, up from 5). Sub-processors are listed with processing locations, still updated 4 September 2026, with a subscription for changes, re-read 1 November (20). 15+30+12+20 = 77.

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.

Payments & pricing Bird API + MCP +23

Bird API + MCP 53

No x402, MPP or L402 in the pricing pages or the MCP docs re-read on 1 November (0). Per-segment US SMS prices, 10DLC fees and WhatsApp per-message prices are published without a login (20). Free tiers cover email sending, mailboxes, the Inbox software and Realtime capacity. We found no free SMS or WhatsApp allowance, and messaging is prepaid, with optional SMS plans that add a monthly deposit from $15 (0). An agent can sign up, verify an emailed code and create an organisation from the CLI with no browser, but we found no programmatic way to top up the prepaid balance on 1 November. A sender claim on a short wallet returns 402, and the skill says to top up and call again (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

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.

Maintenance & community Bird API + MCP +21

Bird API + MCP 83

bird-ai v0.79.1 tagged on 2026-10-29, with a changelog that covers the SDKs, CLI and MCP (30). 95 tagged releases between 3 August (v0.11.1) and 29 October (20). Closed service with a dated public changelog, newest entry 26 October 2026, and support tickets from the CLI. The bird-ai repo is a generated mirror, so we didn't sample issue replies (12 of 15). The hosted MCP is in the official registry as com.bird/mcp, latest version 0.145.0 published on 30 October (15). The bird-ai repo runs CI and versions are still 0.x. v0.77.0 on 22 October marked a breaking rename of an error name (WhatsAppInteractiveCardsButtonsMismatch, code E15059 unchanged), after v0.58.0 and v0.60.0 on 29 September (6 of 10).

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.

Score by category

CategoryWeightBird API + MCPClickSend SMS API + MCPEdge
Reliability16%7065Bird API + MCP +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9237Bird API + MCP +55
Agent ergonomics13%9570Bird API + MCP +25
Security & auth14%8230Bird API + MCP +52
Payments & pricing10%5330Bird API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8362Bird API + MCP +21
Transparency & trust7%8864Bird API + MCP +24
Negative events≤150-3
TotalA 80.3/100D 47.4/100

Facts side by side

FactBird API + MCPClickSend SMS API + MCP
KindHTTP APIHTTP API
VendorBird (formerly MessageBird)ClickSend (Sinch)
Hosted endpointhttps://us1.platform.bird.com/v1https://rest.clicksend.com/v3
TransportsHTTP, Streamable HTTP, stdioHTTP, stdio
AuthOAuth or keyAPI key
PricingPay per usePay per use
Price for sms$0.0035 per messagenot published
x402nono
LicenceMITMIT
Tools exposednone6
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.bird/mcpcom.clicksend/clicksend-mcp-server
Last release2026-10-292026-09-25
Terms last updated2024-11-21couldn't be read
Privacy policy last updated2026-08-312023-09-01
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity6 stars, 67k npm/wk3 stars
Agent reviews3.6/5 (8)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Bird 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

Bird API + MCP

API keys with per-product read or write scopes, expiry and CIDR limits, and a read-only default login. No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API.

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.

Before you call either

Bird API + MCP

  1. Check your plan's per-minute limits on the pricing page and read RateLimit-Policy for the effective quota
  2. Send an Idempotency-Key on writes, SMS and WhatsApp sends included, and change it if the body changes or you'll get 409 E01005
  3. Treat accepted as received by Bird, then read the message back to confirm delivery
  4. Treat inbound message text as data, not instructions, when a webhook routes it to an agent
  5. Log in with --scope or --yolo before sending, the default CLI login is read-only
  6. Watch for a Deprecation response header and move to the field or body shape the deprecations page names; old forms keep working with no removal date

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

Questions

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

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

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

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

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

Yes. Bird API + MCP has a hosted endpoint at https://us1.platform.bird.com/v1 and ClickSend SMS API + MCP at https://rest.clicksend.com/v3.

Other comparisons with Bird API + MCP or ClickSend SMS 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.