MCP for Temporary Emails lets AI agents and automation tools create inboxes, receive emails in real-time, and extract OTPs without writing custom logic.
Unlike traditional temp mail APIs, this adds an MCP layer with high-level actions like “wait for OTP” or “get latest email” — making it seamless for LLMs, agents, and workflows.
Built for developers, QA automation, and AI systems that interact with email-based flows.
FreeCustom.Email now provides a full developer API for creating disposable inboxes programmatically.
Built for testing signup flows, automation, and OTP verification.
Features:
• Automatic OTP / verification code extraction
• Real-time email delivery via WebSockets
• CLI for scripting and automation
• Attachment support up to 50MB
• Custom domain inboxes
• Non-expiring request credits
Free plan available — no credit card required.
Try it live → freecustom.email/api/playground
Hi everyone, I'm Dishant developer of @FCE - Temporary and disposable email
I built it because most disposable email services either track users heavily or have terrible developer experience. My goal was to create a privacy-focused temporary email service with clean UX and a reliable API developers can use for testing, automation, and signup workflows.
Lately I've been exploring the automation + temp mail API space, especially for developers who need disposable inboxes in CI pipelines, QA testing, and automation tools.
Curious to hear from other makers here: Where do you currently use temporary emails in your workflows?
