Ship Email, SMS, WhatsApp, and Voice with Amp and Bird — Bird
Ship messaging and voice from Amp.
Connect Amp to Bird’s MCP server to verify sending domains, wire transactional email, SMS, WhatsApp, and Voice into your codebase, and debug delivery failures without copying API keys or cURL commands.
From prompt to delivered.
Send messages and check delivery from your code, terminal, or AI assistant.
MCP CLI Node.js Python Go PHP Serverless REST
YouVoice
Can you check which calls are active right now and tell me which are connected and which are still ringing?
Bird MCP4 connected actions
- 1 Read the workspace
workspace_get - 2 Find calls in progress
voice_legs_list - 3 Inspect the connected call
voice_legs_get - 4 Inspect the ringing call
voice_legs_get
YouEmail
Send a welcome email to delivered@messagebird.dev from onboarding@messagebird.dev, then check it arrived.
Bird MCP3 connected actions
- 1 Read the workspace
workspace_get - 2 Send the welcome email
email_send - 3 Confirm recipient delivery
email_get
YouSMS
Text the code 123456 to +14155550100 from +15557654321 and check the delivery status.
Bird MCP4 connected actions
- 1 Read the workspace
workspace_get - 2 Send the SMS code
sms_send - 3 Read the message status
sms_get - 4 Check the delivery event
sms_list_events
YouWhatsApp
Send code 123456 to +14155550100 on WhatsApp using our approved bird_otp template, then check it arrived.
Bird MCP4 connected actions
- 1 Read the template catalog
whatsapp_templates_list - 2 Send the approved template
whatsapp_send - 3 Read the message status
whatsapp_get - 4 Check the delivery event
whatsapp_list_events
YouEmail + WhatsApp
Send my test customer a welcome email and WhatsApp code 123456 using our approved bird_otp template, then check both arrived.
Bird MCP4 connected actions
- 1 Send the welcome email
email_send - 2 Send the approved template
whatsapp_send - 3 Confirm recipient delivery
email_get - 4 Read the message status
whatsapp_get
Connect Amp to your Bird workspace with one terminal command and a browser sign-in.
Register Bird’s hosted MCP server once, then authorize your workspace in the browser.
Terminal
Copy command
amp mcp add bird https://mcp.bird.com
Register the Bird MCP server
Run the registration command in your terminal so Amp can reach Bird’s hosted MCP server.
Authorize the connection
Start Amp, and it opens Bird’s sign-in page in your browser. Sign in to choose the workspace permissions to delegate. Amp stores the token and refreshes it when needed.
Check the account
Ask your agent to confirm your signed-in account and active workspace before running your first messaging task. Once it returns your user details and workspace name, you are ready to send test messages and inspect logs.
Ask your agent to diagnose bounces, provision senders, and inspect live traffic.
Paste a prompt in Amp to audit domain DNS records, wire up a new notification channel, or check active calls against your live workspace.
Understand a delivery issue
Check my recent email failures. Group them by reason, inspect the affected sending domain, and tell me what needs fixing before making changes.
Prepare a new channel
Help me set up SMS for order updates. Check my workspace and available senders, explain what is missing, then prepare a test for a number I provide.
See what is happening now
List the Voice calls that are active right now. Separate connected calls from calls that are still ringing, and show their IDs.
How permissions, credentials, and sign-in work
What happens when you authorize Amp to access your Bird workspace and how to troubleshoot a new connection.
Does connecting MCP give my agent unrestricted access?
No. During browser sign-in, you choose which workspace or organization permissions to delegate, and the grant is capped to permissions your account holds. You can revoke the connection anytime from Connected apps in your Bird profile.
Do I need an API key for hosted MCP?
No. Bird’s hosted MCP server authenticates through browser OAuth and refreshes your session token in the background, so no static secret sits in a local config file. When your agent writes application code that sends messages from your own backend, create a dedicated API key for that service.
What if the sign-in page does not open, or the connection stops working?
Amp opens Bird’s sign-in page when it starts after you add the server. If the token is stale or you revoked it, run amp mcp oauth logout bird and start Amp again to sign in, then ask your agent to check your signed-in account and workspace.
Extend your Bird setup across the stack, from hosted MCP tool catalogs and CLI workflow skills to the rest of your coding tools.
MCP server
Call Bird’s live tools over browser OAuth from your IDE, or run the local stdio server alongside the CLI to upload files and manage channels.
Agent skills
Give your coding agent step-by-step CLI playbooks and DNS audit procedures that check domain records and confirm message delivery.
Other AI tools
Connect the same Bird workspace to Claude Code, Cursor, VS Code, Codex, or OpenCode using shared skills and OAuth grants.