Turn generated UI into apps that send transactional email, SMS, and OTP codes.

Connect v0 to Bird’s hosted MCP server so your agent can configure sending domains and run test sends as you build Next.js and React applications. Wire server actions and route handlers for transactional email, SMS notifications, WhatsApp updates, and OTP verification codes, keeping Bird API keys in server-side environment variables instead of client components.

Arrastra un icono sobre los puntos. Usa las teclas de flecha para mover un icono enfocado. Pulsa Escape para cancelar el arrastre.

Del prompt a entregado.

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

TúVoice

¿Puedes comprobar qué llamadas están activas ahora mismo y decirme cuáles están conectadas y cuáles siguen sonando?

Bird MCP4 acciones conectadas
  1. 1Leer el espacio de trabajoworkspace_get
  2. 2Buscar llamadas en cursovoice_legs_list
  3. 3Inspeccionar la llamada conectadavoice_legs_get
  4. 4Inspeccionar la llamada que está sonandovoice_legs_get
Explorar docs de MCP

Connect v0 to Bird’s hosted MCP server before generating your message handlers.

Register the hosted MCP server in v0 and authorize your Bird account with OAuth so your agent can inspect live senders, check domain status, and test deliveries from your workspace.

URL del servidor
https://mcp.bird.com
  1. Añade Bird

    Open MCP Connections in v0 or select Add MCP from the prompt bar, paste the hosted server URL, and choose OAuth as the authentication method.

  2. Autoriza la conexión

    Complete the browser sign-in flow to grant v0 access to your Bird account. Once authorized, v0 can inspect your sending domains, phone numbers, and templates as you iterate on your app.

  3. Verifica la cuenta

    Ask v0 to confirm your signed-in account and active workspace before generating server actions or route handlers. Verifying the workspace upfront ensures test sends and sender lookups run against the right environment.

Take generated v0 interfaces into production Next.js routes. Run sends through server actions and route handlers, authenticate your sending domain, and update your UI from live webhook events.

Keep API keys in server actions and route handlers

Store your Bird API key in server-side environment variables to keep credentials out of browser bundles and client components. Trigger OTP codes, email receipts, and SMS alerts from Next.js server actions or route handlers.

Send from verified domains and approved numbers

Authenticate your sending domain with SPF and DKIM for transactional email, or attach an approved phone number and WhatsApp sender so customer notifications reach the inbox and handset.

Surface live delivery status via webhooks

Store the message ID returned when your route handler sends a message, then receive Bird delivery and bounce webhooks to update order confirmations, onboarding steps, or verification screens.

Prompts to test senders and debug delivery while you build in v0.

Ask v0 to inspect your Bird workspace, verify sending domains, or diagnose failed deliveries before wiring the next screen in your app.

Entiende un problema de entrega
Revisa mis fallos de correo recientes. Agrúpalos por motivo, inspecciona el dominio de envío afectado y dime qué hay que corregir antes de hacer cambios.
Prepara un nuevo canal
Ayúdame a configurar SMS para actualizaciones de pedidos. Revisa mi espacio de trabajo y los remitentes disponibles, explícame qué falta y prepara una prueba para un número que te proporcionaré.
Mira qué está pasando ahora
Lista las llamadas de Voice que están activas ahora mismo. Separa las llamadas conectadas de las que aún están sonando y muestra sus ID.

Common questions about v0 and Bird

How OAuth workspace access in v0 relates to the server-side API keys your deployed Next.js app uses in production.

¿Conectar MCP le da a mi agente acceso sin restricciones?

No. Bird’s hosted MCP server runs with the account permissions you approve during OAuth sign-in, scoped to your workspace. You can inspect or revoke v0’s access from your Bird account settings whenever you need to.

¿Necesito una clave de API para MCP alojado?

You do not need an API key to connect v0 to the hosted MCP server, which authenticates through browser OAuth. When you deploy the Next.js app you built in v0, store a dedicated Bird API key in your server-side environment variables so your server actions and route handlers can send email, SMS, WhatsApp messages, and OTP codes.

¿Qué pasa si las herramientas aparecen pero las llamadas fallan?

Check that the OAuth sign-in step completed in v0. Adding the MCP server URL lists Bird’s tools, and completing browser authorization links them to your workspace. Reauthorize the Bird connection in v0 and ask your agent to confirm the signed-in account and active workspace.

Extend your Bird setup across the rest of your AI workflow. Pair the hosted MCP server with reusable agent skills, or connect the same Bird workspace to your code editor and terminal.

Servidor MCP

Review how Bird’s hosted MCP endpoint handles OAuth sign-in, workspace scoping, and tool permissions for inspect and send operations.

Habilidades del agente

Load task-focused instructions for Bird APIs, webhook signature verification, and channel payloads so your coding agent writes accurate server routes.

Otras herramientas de IA

Connect Cursor, Claude Code, Windsurf, or Codex to the same Bird workspace when you move your v0 project into a local repository.

Start building with Bird in minutes.