# Your Replit app can send email

Bird is in Replit Agent's MCP list, so the setup is one sign-in. Agent then writes the call, one secret carries the key, and the app sends through Bird from the first run.

## Connect Bird, then ask for the email

Connecting Bird over MCP hands the agent the tools to finish the setup itself: it mints the key, stores it, and proves the send. Your own domain is the step before launch, not before the first test.

Signing in to Bird from the MCP Servers list at replit.com/integrations

**in the chat**

```bash
> Add Bird email to this app. Create an API key for it,
> store it as a Replit secret, and send me a test from
> onboarding@messagebird.dev so I can watch it land.

# Replit Agent mints the key over MCP; it never passes through the chat
```

**in the chat**

```bash
> Add acme.dev as a sending domain and give me the DNS
> records to publish. Once they resolve, verify it and
> switch the from address to hello@acme.dev.

# Agent creates the domain, reads the records back and
# verifies over MCP. Nothing to do in the dashboard.
```

## Three things and it works. Agent talks to Bird over MCP. The app it builds talks to Bird with these three.

- A key, kept server-side. One key carries the region and the permissions. Store it as a secret so it never reaches the browser.
- A sender you are allowed to use. Start on the onboarding domain, move to your own when you launch. Sending from an unverified domain bounces.
- One call per message. The SDK reads the region from your key, so there is no host to configure. A send returns accepted, and delivery follows.

### What to ask for

- Connect to Bird and send me a test email from onboarding@messagebird.dev.
- Text the customer when their order ships.
- Send a password reset link that expires in an hour.
- Email the admins a weekly digest of new signups.
- Verify phone numbers at signup with a code over SMS.
- Show delivery status on the admin page, updated from Bird's webhooks.