MessageBird
Send SMS, voice messages, and one-time verification codes, and look up phone numbers via MessageBird (now part of Bird).
About
MessageBird ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.messagebird- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Communication
Overview
MessageBird — now part of Bird — sends SMS and text-to-speech voice messages, runs phone-number verification (OTP) flows, and looks up carrier/line-type data for a number, all through its classic REST API at rest.messagebird.com.
Send SMS covers plain, binary, and flash message types with scheduling and delivery-report callbacks. Voice message send converts text to speech and places an outbound call reading it, with machine-answer handling and repeat count. The Verify actions cover both halves of an OTP flow: requesting a code (by SMS, TTS, or email) and checking the code a user typed back in. Lookup resolves a phone number to its country, carrier line type, and canonical formats without sending anything — useful for validating a number before spending on an SMS or voice send.
MessageBird’s brand and marketing now live under Bird (bird.com), and its status page moved to status.bird.com, but this classic REST API (rest.messagebird.com, AccessKey auth) remains the live, documented surface these actions use — this app does not call Bird’s newer unified messaging API.
Build with MessageBird
Three routes to the same 7 actions. The Workflow tab is generated from MessageBird's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Check Verification Code
verify-check Verify the one-time code a user entered against a Verify request.
Request Verification Code
verify-request Send a one-time verification code to a phone number or email address.
Send Voice Message
voice-message-send Call one or more recipients and read a text-to-speech message aloud.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying MessageBird's real ids.
{
"manifestVersion": "2",
"name": "messagebird-example",
"steps": [
{
"id": "lookup-number",
"uses": {
"app": "io.w6w.messagebird",
"action": "lookup-number",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"phoneNumber": "<phoneNumber>"
}
}
]
}Here are some of the things you can do
-
Look Up Number
readlookup-number -
Get Message
readmessage-get -
List Messages
searchmessage-list -
Send SMS
performsend-sms -
Check Verification Code
performverify-check
+2 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for MessageBird, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to MessageBird. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "lookup-number",
payload: {
phoneNumber: "<value>",
// countryCode: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action lookup-number --payload '{"phoneNumber":"<value>"}'Give an AI agent MessageBird — without giving it MessageBird's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.messagebird#lookup-number",
"input": {
"phoneNumber": "<phoneNumber>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's MessageBird connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
MessageBird's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. MessageBird itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
MessageBird declares its own checks, so its health is a property of the app rather than something the host guesses at.
MessageBird (Bird) platform status
Atlassian Statuspage rollup for status.bird.com, scoped to the SMS API and Voice API components. Unauthenticated and unsigned.