Hey Product Hunt 👋 I've been using Resend for everything I ship. It's a great sending API for my entrepreneurial endeavors . Every time someone replied to a transactional email, that reply went into a webhook payload and then nowhere. My "support@" address was really just a forwarding rule and some hope I would check incoming. So I built the client half. You paste your own Resend API key, inboxes imports your full history, and you get an actual inbox for every domain - threading, full-text search with from: / has:attachment operators, undo send, scheduled send, snooze, rules, shared aliases, roles. Discord-style sidebar, Cmd+1-9 to switch domains. Gmail shortcuts, because muscle memory is real. Agents get an inbox too. There's an MCP server for Claude Code, Codex, opencode etc. Your agent reads, searches, and writes drafts as you, with your permissions. Sending is one org-level switch, off by default, enforced server-side. Draft-first by default so it's opt-in only $5/mo per org, unlimited members and domains. Or self-host free - open source, same feature set, MCP included. What's your current setup for reading replies to app email? I want to know if I'm the only one who was doing this by hand!

inboxes.net - Gmail+Discord Resend inbox

Open-source, multi-domain inbox and agent MCP for Resend

Open-source, multi-domain inbox and agent MCP for Resend