AI / Base44

Your Base44 app can send email

Add Bird as a custom MCP connection and Base44's chat builds with live context. Keep the key in server-side code, and the approval tool you built can tell people it needs them.

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.

Base44 Settings
  1. Profile
  2. Settings
  3. MCP connections
  4. Add custom MCP
Name
Bird
URL
https://mcp.bird.com
Authentication
OAuth

Test & add opens the consent screen. Custom MCPs need a Builder plan or higher.

Three things and it works.Base44's chat talks to Bird over MCP while it builds. The app it ships 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.

$ Developers → API keys

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.

$ onboarding@messagebird.dev

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.

$ npm install @messagebird/sdk

What to ask for

Empieza con un canal.
Añade los demás cuando estés listo.

Una clave API de prueba es tuya de inmediato. El acceso a producción se desbloquea cuando añades un método de pago y verificas un remitente.

¿Usas Claude Code, Cursor o Codex? Copia un prompt de configuración y tu agente instalará el Bird CLI y las habilidades por ti. Elige el tuyo:

Cursor