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.

CommencerContacter l’équipe commerciale

Glissez une icône sur les points. Utilisez les touches fléchées pour déplacer une icône sélectionnée. Appuyez sur Échap pour annuler le glissement.

Du prompt à livré.

Send messages and check delivery from your code, terminal, or AI assistant.

VousVoice

Pouvez-vous vérifier quels appels sont actifs en ce moment et me dire lesquels sont connectés et lesquels sonnent encore ?

Bird MCP4 actions connectées
  1. 1Lire l'espace de travailworkspace_get
  2. 2Rechercher les appels en coursvoice_legs_list
  3. 3Inspecter l'appel connectévoice_legs_get
  4. 4Inspecter l'appel en sonnerievoice_legs_get
Explorer la documentation MCP

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.

Lire le guide de configuration
URL du serveur
https://mcp.bird.com

  1. Ajouter Bird

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

  2. Autoriser la connexion

    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. Vérifier le compte

    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.

Comprendre un problème de livraison
Vérifiez mes échecs d'envoi d'e-mails récents. Regroupez-les par motif, inspectez le domaine d'envoi concerné et dites-moi ce qu'il faut corriger avant d'apporter des modifications.
Préparer un nouveau canal
Aidez-moi à configurer SMS pour les mises à jour de commandes. Vérifiez mon espace de travail et les expéditeurs disponibles, expliquez ce qui manque, puis préparez un test pour un numéro que je fournis.
Voir ce qui se passe maintenant
Listez les appels Voice actifs en ce moment. Séparez les appels connectés de ceux qui sonnent encore, et affichez leurs identifiants.

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.

Connecter MCP donne-t-il un accès illimité à mon agent ?

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.

Ai-je besoin d'une clé API pour le MCP hébergé ?

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.

Que faire si les outils apparaissent mais que les appels échouent ?

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.

Serveur MCP

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

Compétences de l'agent

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

Autres outils IA

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

Start building with Bird in minutes.

CommencerContacter l’équipe commerciale