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.

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 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.

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

  1. Add 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. Authorize the connection

    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. Check the account

    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.

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 v0 and Bird

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

Does connecting MCP give my agent unrestricted access?

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.

Do I need an API key for hosted MCP?

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.

What if the tools appear but calls fail?

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.

MCP server

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

Agent skills

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

Other AI tools

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.

Get StartedContact Sales