# Build web apps that send email, SMS, and verification codes.

Connect Lovable to Bird while you build to configure sending domains, run test deliveries, and wire up transactional email, SMS notifications, WhatsApp messages, and OTP verification through server-side functions.

Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.

## 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. **1** Read the workspace `workspace_get`
2. **2** Find calls in progress `voice_legs_list`
3. **3** Inspect the connected call `voice_legs_get`
4. **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. **1** Read the workspace `workspace_get`
2. **2** Send the welcome email `email_send`
3. **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. **1** Read the workspace `workspace_get`
2. **2** Send the SMS code `sms_send`
3. **3** Read the message status `sms_get`
4. **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. **1** Read the template catalog `whatsapp_templates_list`
2. **2** Send the approved template `whatsapp_send`
3. **3** Read the message status `whatsapp_get`
4. **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. **1** Send the welcome email `email_send`
2. **2** Send the approved template `whatsapp_send`
3. **3** Confirm recipient delivery `email_get`
4. **4** Read the message status `whatsapp_get`

## Add Bird to Lovable

Add Bird as an MCP server in Lovable’s Connectors and sign in to your workspace. Lovable can then add email, messaging and verification to your app as you build, with only the permissions you approve.

## Connect Lovable to your Bird workspace directly from Connectors.

Point Lovable at Bird's hosted MCP server and sign in with OAuth so your agent can inspect senders, configure domains, and run test deliveries in the right workspace.

### Server URL
```
https://mcp.bird.com
```

1. **01**  **Add Bird**  
   Open Connectors → + → MCP server in Lovable. Name the connection Bird, paste the hosted server URL, and keep OAuth selected.
2. **02**  **Authorize the connection**  
   Choose Add & authorize to sign in through your browser and grant Lovable access to your Bird workspace.
3. **03**  **Check the account**  
   Ask Lovable to confirm your signed-in account and active workspace before starting your first messaging task so domains, senders, and test deliveries use the right environment.

## Connect Bird to Lovable today

Add `https://mcp.bird.com` as an MCP server in Lovable's Connectors to start configuring senders and testing messages in minutes. Prefer a built-in connector in Lovable's directory? Let us know, and we'll notify you when it launches.

## Take your Lovable app from prototype to production.

Call Bird from server-side edge functions, send from your own domain or phone number, and update your interface as messages arrive.

### Keep the key on the server

Store your Bird API key in backend environment secrets and trigger emails, SMS notifications, or OTP codes from server-side edge functions so credentials stay out of browser bundles.

### Use a sender you control

Authenticate your sending domain with DNS records or configure an approved SMS or WhatsApp sender so customer notifications and verification codes reach the inbox.

### Show the real result

Receive Bird webhooks in your backend when an email bounces, an SMS lands, or a verification succeeds, and reflect the live status directly in your app.

## Start with prompts that configure senders and inspect live delivery.

Paste these prompts into Lovable to inspect bounced emails, set up SMS order alerts, or check active voice calls against your live Bird 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.
```

## Questions about connecting Lovable to Bird

### Does connecting MCP give my agent unrestricted access?

No. When you authorize Bird from Lovable's Connectors, the MCP server runs with your signed-in account permissions and the scopes you approve for that workspace. You can disconnect or revoke Lovable's access from your Bird account settings whenever you need to.

### Do I need an API key for hosted MCP?

No API key is needed to connect Lovable itself, because the hosted MCP server authenticates through OAuth in your browser while you build. When your published Lovable app sends transactional emails, SMS alerts, or OTP codes for real users, store a dedicated Bird API key in your backend secrets so requests run from server-side functions.

### What if the tools appear but calls fail?

Adding the MCP server URL in Connectors registers the tools, and completing the OAuth sign-in authorizes them to call your workspace. If tool calls fail, open Connectors in Lovable, reauthorize the Bird connection, and ask Lovable to confirm your signed-in account and active workspace before retrying.
