Cloudflare Email Service: now in public beta. Ready for your agents
Chapters8
Overview of the new Cloudflare email service for agents and the ability to send and receive emails.
Cloudflare Email Service is in public beta, adding agent-accessible sending, inbound routing, and developer tools like Wrangler CLI and MCP support.
Summary
Thomas, Cloudflare’s product manager for the email service, introduces Cloudflare Email Service’s public beta and emphasizes agent-focused features. The update enables both outbound sending and inbound receiving for top-level and subdomains, integrated with existing email routing. A practical demo shows a sample app using a send email binding in wrangler.json, illustrating how any worker can send email via the Cloudflare backend. The REST API is highlighted as a way to configure and send emails from external servers or on-prem environments. Agents Week reveals new capabilities: Wrangler CLI access for agents to trigger email sends, and MCP support so clients can auto-call the REST API without extra setup. Cloudflare also showcases an open-source reference app with full email threading, drafts, and storage, designed to help teams build agent-enabled email experiences. Thomas notes that the open-source inbox helps triage private beta requests and serves as a foundation for integrating agents with email. The session closes by pointing viewers to blog posts and GitHub resources linked in the blog for deeper exploration and onboarding.
Key Takeaways
- Public beta of Cloudflare Email Service is live, with sending and receiving for domains and subdomains.
- Email sending bindings can be used from workers by configuring wrangler.json and invoking the send email binding.
- REST API endpoints exist to configure and send emails, complementing the Worker bindings.
- Wrangler CLI now supports agent-driven email sending via wrangler email sending send.
- MCP support enables clients (or tools like Claude or ChatGPT) to call the Cloudflare REST API without extra configuration.
- An open-source reference inbox app demonstrates drafts, storage, and conversational threading for agent-assisted email management.
- The solution includes an agent SDK and a reference app available on GitHub and linked in the Cloudflare blog.
Who Is This For?
Developers and product teams building agent-enabled workflows, email bots, or internal tools who want to send/receive email via Cloudflare and integrate with external systems using MCP or REST APIs.
Notable Quotes
""Hello from Agents Week demo.""
—Example of sending an email via the demo setup using the Wrangler binding.
""Hello world from Agents Week demo.""
—Demonstrates successful email delivery from the sample inbox.
""Use the Cloudflare API MCP to send an email from my personal email to this test inbox""
—Shows MCP-based email sending against a personal-domain setup.
""We actually have this available via the REST API""
—Highlights the REST API option for external/onsite integrations.
""This is an open-source application that you can fork""
—Points to the reference inbox app as a starting point for developers.
Questions This Video Answers
- how do I send emails using Cloudflare Wrangler in the public beta?
- what is Cloudflare MCP and how does it work with the email service?
- can I use Cloudflare Email Service with external servers or on-prem systems?
- how do drafts and storage work in Cloudflare's agent-enabled email app?
- where can I find the open-source reference inbox for Cloudflare email service?
Cloudflare Email ServiceAgent WeekWrangler CLIMCP (Cloudflare API)REST APIEmail bindingsOpen-source email clientEmail drafts and storage
Full Transcript
[music] Everyone, welcome to Agents Week. I, like so many of you, is are re- really excited about this week. Today, we're going to be talking about email and how we can give email to our agents. My name is Thomas. I'm the product manager for the email service team, and today I want to share with you some of the announcements that we're we're rolling out today with email all about giving agents email access so that they can send and receive emails. So, I'm sure that you've already seen our previous announcement for the private beta, and we've been iterating to get us to public beta, and I want to share with you what we have ready for you today.
So, let me go ahead and share my screen. So, here we are with the Cloudflare email service. It's now available. These are the docs. It'll be available for you in the dashboard. Let me share with you what that looks like. If you head on over to the email service tab, you'll be able to see your account, and in here I've already been using this for a while now. You can see your analytics, the the logs, and the settings. And so, you can onboard either a top-level domain or subdomain. And now, this sending part really complements our existing email routing.
And so, this way you can have both sending outbound emails and receiving inbound emails. And this becomes really powerful. Now, for the purposes of this demo, I have what I've gone ahead and created a sample inbox just so I can share with you the the sending of the emails. I'll give you more details into this later today. Um, but what I'm first going to do is I'm going to share with you email sending, right? You That's probably what you want to see. So, I have a sample application that I've built out here. It's pretty basic.
I went ahead and and created this vibe coded this with with open code yesterday. But, I want to share with you how email works. So, if you take a look at wrangler.json, you'll see that I have added the send email binding. And when we add the send email binding, that'll allow you to from any worker be able to go ahead and send an email, right? So, in this case, pass in the to, the from, and the subject. Um, and I actually have a a couple different options. And so, if I want to show you what that looks like, I can go over to my app this running here, and then I can decide, "Hey, I want to send an email to the test inbox that I have here.
So, let's set this here. We'll send it from my domain, which I've onboarded, right? This is what I was sharing with you here. This is my personal domain, and I will be sending an email from this personal domain to the test inbox that I've created. So, we can just say, "Hi from Agents Week demo." And anybody works, of course. And then, just like that, this will actually send the email. Now, what you may have noticed is that I want to share with you this. This is using remote binding, so it's automatically going to be using the actual email sending capability in Cloudflare.
And if we go ahead and refresh our inbox, boom, just like that, you can see the hello world from Agents Week demo. Um, so that's very simple, but this is from the workers binding. I know a lot of you are also looking to use this from an external server or an external resource or even from from on prem. And so, we actually have this available via the REST API. I want to show you the the REST API actually. So, let me go to api.cloudflare.com. And if you head on over here, you'll be able to see you have all of the endpoints to go ahead and not only configure, but also send emails.
And all of this is documented in these docs for Cloudflare email service. But, as you know, this is Agents Week, and we have a couple interesting tidbits as part of Agents Week that really really elevate the bar for what you can do with email and giving email to your agents. The first thing that we shipped is, let me see, let me bring you over here. Let's say you wanted to give access to a coding agent the ability to send you an email. Let's say whenever a build completes or send you a notification. Well, the first thing that we've done is we've given you the ability or given the agents the ability to use the wrangler CLI in order to send off the email.
So, as you know, a lot of folks have been giving CLI access in order to give the give your actual agent tools. And so, in this case, they can call wrangler email sending send. So, we can just go ahead and do it again and say, "Hello from Agents Week demo." And so, this is going to use the wrangler CLI. It's available. Just go ahead and install wrangler CLI on the machine on which your agent is running, and then just like that, it'll once again, if we go ahead, boom, and it's already loaded, right? Okay. Um, now that is the wrangler CLI, but as you know, tooling would be incomplete without an MCP.
And we also have MCP support for email. Now, as you may be aware, we have a pretty large MCP. Let me bring over the the Cloudflare MCP server. The the code mode MCP. So, if I go over to Cloudflare/mcp, you'll see that this is a MCP server for all of the open API spec, all of the REST API for for the Cloudflare REST API surface. And essentially, if you go ahead and add the Cloudflare API, you give it the right permissions, it'll then be able to go ahead and search and then call the right API without any additional configuration.
So, this is just a simple MCP that you can add to any client. You can add it to Claude, you can add it to ChatGPT, and or any coding agent. So, in this case, we went ahead and said, "Hey, use the Cloudflare API MCP to send an email from my personal email to this test inbox that I've created." And let's go ahead. Let's send another one from Agents saying, "Hi from Agents Week demo using Cloudflare API MCP." Um, and this will once again use the the MCP in order to send the email. As you can see here, it's sending.
It says it sent successfully. Let me go back to the inbox, and boom, there you go. So, this is the the capability that that we've provided out of the box with email service for agents. Um, we've also written written a set of skills that you can give your agent either to use email service to send emails or build applications on top of emails. And speaking of applications, this is the the last thing that I want to share with you. As part of this iteration process, we've we've been spending a lot of time learning about, well, what does it mean when you when you give email to your agents?
And very importantly, what we've found is that when you interact with agents and emails, you often want to be in the loop, right? You want to see what is the agent going to draft? Uh, how can I give agent the ability to go and look at my past emails? And so, that's a bit more than the raw APIs to send and receive emails. You might actually want to have storage of of email, storage of attachments, storage of drafts. Um, and this is what we've built here. So, this was the test inbox that I've been sharing with you since the start.
But, what we've what we've done is we've augmented this with agents. So, if you take a look at this here, you'll see that on each email that I've been receiving, um, the agent has been drafting an auto reply. And so, obviously, I've I've sent this one a couple of times, but you can see that this is a draft reply that the agent has come up with. And at this point, what I can do is decide whether to send or edit, right? Because the thing is, I don't want the agents to respond before I've had the chance to take a look at it and make sure everything is good.
And so, this is available within the app. The agent can go ahead and create a draft, and then I can decide whether to send the email or not. And all of this is an application that you can deploy yourself. You can fork it. It's available as an open-source application. Everybody that that we've been speaking to over the course of this private beta is trying to rebuild a form of an email client and then augmenting it with agents. And so, this email client is a really solid foundation for you to start. It has full conversational threading for email conversations, and it showcases how you can use the agent SDK, but also add MCP support in case you want to not only have an agent within your inbox, but also give that inbox to a local agent.
So, this is is a very good reference application that you can go ahead and fork and use it. I've been using it for the past couple weeks in order to to triage all of the the requests for email service private beta, but it's been it's been great, and this has really helped me manage the the the influx, but this is also a very good reference application. So, feel free to take a look. This is available on our GitHub today, and Um, it's also linked in the blog. So, on that note, uh, that wraps up all that I had to say for Cloudflare email service.
Uh, thank you so much for watching. I think that it's a very exciting time giving agents more and more functionality to do more and more work. Um, make sure not to miss any of our other announcements as part of Agent Week. Uh, the blog posts are are coming through and through. Um, and uh, yeah, I think it's it's going to be a a great one. Thanks so much for watching.
More from Cloudflare
Get daily recaps from
Cloudflare
AI-powered summaries delivered to your inbox. Save hours every week while staying fully informed.







