Connect Muse to Bird · Send messages and inspect delivery from chat — Bird
Send messages and manage channels from your Muse chat session.
Connect Muse to the Bird MCP server as a custom connector to send email, SMS, and WhatsApp messages, configure sending domains and phone numbers, and inspect delivery and bounce events in your Bird workspace.
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 Muse to your Bird workspace in three steps.
- Add the Bird connector in chat
Paste the setup prompt into a Muse chat session so Muse registers the hosted Bird MCP server as a custom connector.
- Approve workspace access in your browser
Muse replies with a session authorization link. Open the link in your browser and approve Bird’s consent screen to grant delegated access to your workspace. Because the link is tied to your session, ask Muse for a fresh link if it expires.
- Confirm your account and workspace
Ask Muse to verify your signed-in account and active Bird workspace before sending messages or changing channel settings. Once Muse returns your account details, you are ready to inspect domains, numbers, and delivery logs.
Debug delivery, configure senders, and monitor live traffic from chat.
Ask Muse to inspect bounce reasons on your sending domains, check SMS sender readiness before a launch, or list active voice calls in your 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 and session sign-in work in Muse.
Does connecting Muse give the agent unrestricted access to my workspace?
No. Muse operates within the Bird account permissions you hold and grant on the browser consent screen. You can review or revoke the delegated connection from your Bird account settings whenever your team's access needs change.
Do I need to generate a Bird API key to use Muse with hosted MCP?
No. When you connect Muse to the hosted Bird MCP server, you sign in through your browser with a session authorization link instead of copying static API keys into chat. Deployed backend services and automated pipelines still use dedicated Bird access keys.
Why do Bird tools appear in Muse when requests still fail?
Adding the custom connector URL in Muse loads the tool definitions, while your workspace remains unauthenticated until you open the authorization link and approve the consent screen. Ask Muse for a fresh session authorization link, complete browser sign-in, and ask Muse to confirm your signed-in account and active workspace.
Extend your Bird setup across AI tools.
MCP server
Review how the hosted Bird MCP server handles browser OAuth, workspace permissions, and live tool calls across email, SMS, WhatsApp, and Voice.
Agent skills
Install reusable Bird skills so your coding agent writes webhook handlers, API requests, and channel setup code against current schemas.
Other AI tools
Connect Claude, Cursor, Windsurf, Codex, and other MCP clients to the same Bird workspace for code generation and live channel debugging.