Inbound email. Keep talking.

Give customer replies a place in your application. Receive email on your domain or a forwarding address, retrieve its body and attachments, and let your app or agent take the next step.

Trusted every day by teams that
build world-class software.

A reply arrives.
Your agent has context.

Ask Bird MCP to find the customer’s reply and read the message. Your agent can work with the actual email and its attachments, alongside the application context you provide.

Find the latest reply
and read the message.

Bird MCP
  1. email_inbound_messages_listFound
  2. email_inbound_messages_bodyLoaded
Maya Lingmaya@example.com
Re: Your Harbor order

A reply. With context.

Could I collect this from the studio tomorrow?

In reply toHB-2048

Read the message.
Keep the details.

Inspect the rendered email, plain text, headers and original message in Bird. Authentication results and reply references help your team understand what arrived before taking the next action.

Access the original message when you need the complete MIME source.

Ready to build?

Receive the reply.
Build what happens next.

Receive email on your domain or a forwarding address. Use the webhook’s message reference to fetch the body and attachments.

A reply belongs
to a conversation.

Use the sender, subject and reply references to connect incoming mail to an order, support case or account in your application. Fetch the body and attachments when your team or agent needs to act on the customer’s request.

Inbound email, explained.

Do I need a domain to receive email?

No. A generated forwarding address lets you forward an existing inbox without DNS changes. Receiving directly on your own subdomain requires its MX records.

Does the webhook include the whole message?

The email.received webhook contains message metadata and its inbound message ID. Fetch the body, attachments or original MIME through the inbound-message API when you need them.

How long are received messages retained?

Received messages are retained for 30 days. If your application needs a longer history, retrieve and store the required data under your own retention policy.

Scale without losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

Go further.
With Email.

Everything from your first send to delivery at scale.

Start with one. Build across channels.

Bring your next customer conversation into the same workspace.

Your next idea. Ready to connect.

Your next idea. Ready to connect.