Build Base44 apps that send email, SMS, WhatsApp, and verification codes.

Connect Base44 to Bird while you build internal tools, customer portals, and business apps. Configure sending domains and channels from your workspace, keep live API credentials on the backend, and track delivery statuses as messages reach your users.

Get StartedContact Sales

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.

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. 1Read the workspaceworkspace_get
  2. 2Find calls in progressvoice_legs_list
  3. 3Inspect the connected callvoice_legs_get
  4. 4Inspect the ringing callvoice_legs_get
Explore MCP docs

Connect Base44 to your Bird workspace in three steps.

Link Bird's hosted MCP server to Base44 with OAuth so your agent can inspect your workspace, verify senders, and wire up messaging while you build.

Read the setup guide
Custom MCP connection
https://mcp.bird.com

  1. Add the hosted MCP server

    Enter Bird's hosted MCP URL in your Base44 workspace MCP connection settings and select OAuth as the authentication method.

  2. Authorize your Bird workspace

    Complete browser OAuth sign-in to grant access to your Bird workspace, then enable the Bird connection in the Base44 app you are building. Custom MCP connections require the Base44 Builder plan or higher.

  3. Confirm the active workspace

    Ask the Base44 agent to check which Bird account and workspace are signed in before you start building. Confirming the active workspace ensures new senders, templates, and tests run in the right environment.

Take your Base44 app from workspace prototype to live customer traffic. Run live email, SMS, WhatsApp, and verification calls through backend secrets, verified senders, and webhook delivery tracking.

Keep API credentials on the backend

Store your Bird API key in your app's server-side environment secrets and call Bird from backend routes to keep live credentials out of browser code when sending emails, SMS alerts, or verification codes.

Send from verified domains and numbers

Verify your sending domain and configure approved SMS or WhatsApp senders in Bird before launch so customer notifications, receipts, and sign-in codes pass carrier and inbox checks.

Track real delivery events in your app

Store the Bird message ID when your app sends a message and subscribe to delivery webhooks so internal dashboards and customer portals show whether a message was delivered, bounced, or failed.

Start with prompts that inspect senders, configure channels, and debug delivery.

Ask the Base44 agent to check sending domains, set up SMS or WhatsApp for your app, and inspect live delivery or call status against your 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.

What to know before connecting Base44 to Bird.

How workspace permissions, OAuth sign-in, and backend API credentials work when you build and deploy Base44 apps.

Does connecting MCP give my agent unrestricted access?

No. The hosted MCP connection runs with the Bird user role and workspace permissions you approve during OAuth sign-in, and it cannot exceed your account's access. You can revoke the Base44 connection at any time from your Bird account settings.

Do I need an API key for hosted MCP?

You do not need an API key to use Bird's hosted MCP server while building in Base44 because the MCP connection authenticates through browser OAuth. When you publish your Base44 app for users, configure a server-side Bird API key in your app's backend secrets so deployed routes can send messages.

What if the tools appear but calls fail?

Check that OAuth authorization completed in your Base44 workspace settings and that the Bird connection is selected for your current app. Saving the MCP server URL adds the tool definitions, and completing the OAuth sign-in allows the agent to run requests against your active Bird workspace.

Extend your Bird setup across the rest of your AI workflow. Review MCP permissions, add reusable agent skills for Bird APIs, or connect another coding environment to the same workspace.

MCP server

Review how Bird's hosted MCP server handles OAuth sign-in, workspace scoping, and tool permissions.

Agent skills

Install reusable Bird skills so your coding agent follows verified patterns for email, SMS, WhatsApp, and webhooks.

Other AI tools

Connect editors and agents like Cursor, Claude Code, and Windsurf to the same Bird workspace.

Start building with Bird in minutes.

Get StartedContact Sales