What problem does it solve? Integrating transactional email into applications requires navigating Cloudflare Email Service setup, domain onboarding, binding configuration, and deliverability rules, where outdated knowledge leads to misconfigured sends and bounced messages. ## Core Features & Use Cases - Email Sending: Send transactional emails from Cloudflare Workers via the send_email binding, from external apps via the REST API, or from coding agents via wrangler CLI and MCP tools. - Email Routing & Receiving: Process inbound emails with the Workers email() handler, forward to verified destinations, parse MIME content with postal-mime, and build store-and-reply workflows with Durable Objects. - Deliverability Management: Configure SPF/DKIM/DMARC, monitor bounces and suppression lists, and query email analytics through the GraphQL Analytics API. - Use Case: Add a welcome email to a Cloudflare Worker by onboarding the domain with wrangler email sending enable, adding the send_email binding to wrangler.jsonc, and calling env.EMAIL.send() with HTML and text bodies. ## Quick Start Ask the agent to add email sending to your Cloudflare Worker using the send_email binding and the cloudflare-email-service skill.