Ship full-stack Bolt apps with transactional email, SMS, and verification.

Connect Bolt to Bird while you generate your app so you can verify sending domains, keep Bird API credentials in server-side environment secrets, and test live email, SMS, WhatsApp, and OTP delivery before publishing.

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 Bolt to your Bird workspace in three steps.

Register Bird's hosted MCP server in Bolt and sign in through your browser so your agent can inspect senders, configure channels, and test delivery while building your app.

Read the setup guide
Server URL
https://mcp.bird.com

  1. Add Bird

    Copy the hosted MCP server URL above and choose OAuth when Bolt prompts for an authentication method.

  2. Authorize the connection

    In Bolt, open + → Connectors → Manage connectors → Custom MCP server. Name the connector Bird, paste the server URL, choose HTTP and MCP OAuth, then click Connect. Enable Bird in your project's Connectors menu.

  3. Check the account

    Ask Bolt to confirm your signed-in Bird account and active workspace before generating messaging code. Seeing your workspace details verifies that OAuth succeeded and your project is targeting the right senders.

Move your Bolt app from workspace preview to live customer delivery. Keep Bird API keys in server-side environment secrets, send from verified domains and numbers, and update your UI from real webhook events.

Keep API keys in server secrets

Store your Bird API key in your backend environment secrets so credentials stay out of browser bundles. Have your Bolt frontend call your own server routes, which then send email, SMS, WhatsApp, or OTP requests through Bird.

Send from verified domains and numbers

Verify your sending domain with DNS records for transactional email, or attach an approved phone number or WhatsApp sender before taking your Bolt app live.

Track delivery with webhooks

Persist the Bird message ID returned when you send and subscribe to webhook events so your app reflects real delivery, bounce, and verification status.

Start with prompts that inspect and configure your messaging channels.

Ask Bolt to diagnose email delivery issues, check SMS sender readiness, or inspect active voice calls using live data from 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.

Common questions about connecting Bolt and Bird.

Understand how OAuth workspace access in Bolt differs from the server-side API keys your deployed application uses.

Does connecting MCP give my agent unrestricted access?

No. Bolt operates within the Bird account permissions and workspace access you grant during OAuth sign-in. You can review or revoke the connector authorization 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 the hosted MCP server in Bolt, because the connector authenticates through browser OAuth. When you deploy the web app you built in Bolt, create a dedicated Bird API key and store it in your backend environment secrets so your server routes can send email, SMS, WhatsApp, and OTP messages.

What if the tools appear but calls fail?

Verify your connector authentication state in Bolt. Adding the MCP server URL registers the tool definitions, and completing the OAuth sign-in authorizes requests to your workspace. Reconnect Bird in your project's Connectors menu, then ask Bolt to confirm your signed-in account and active workspace.

Extend your Bird setup across the rest of your development workflow. Explore MCP transport details, reusable agent skills, and integrations for your code editor or terminal.

MCP server

Review HTTP transport, OAuth token scopes, and workspace permissions for Bird's hosted MCP endpoint.

Agent skills

Install reusable Bird skills so coding agents generate accurate API calls, webhook handlers, and channel configurations.

Other AI tools

Connect the same Bird workspace to Cursor, Claude Code, Windsurf, and other AI development environments.

Start building with Bird in minutes.

Get StartedContact Sales