Automate Agent Email Verification with Open-Source MoeMail Model Context Protocol Server
MoeMail released an open-source Model Context Protocol server and command-line interface to solve agent signup verification blocks. It manages temporary inboxes and handles polling delays as structured data rather than failing with runtime errors.
Impact: High
Why it matters
You can now run end-to-end user onboarding tests in Claude Code or Cursor without manually copying one-time verification codes.
TL;DR
- 01Install @moemail/mcp via stdio to give Claude Code and Cursor disposable email verification capabilities.
- 02Design MCP tools to return waiting states and polling timeouts as structured data rather than throwing exceptions.
- 03Use moemail skill install to auto-configure the create-wait-read-delete loop in Codex and Claude Code.
Key facts
- MCP Tools Registered
- 8 tools
- Blocking Timeout Window
- Up to 90 seconds
- Package License
- MIT
- Self-Host Infrastructure
- Cloudflare Workers
Overcoming the Agent Inbox Bottleneck
Autonomous testing agents in Claude Code, Cursor, and Codex frequently fail during registration workflows because they lack access to an email inbox. The open-source @moemail/mcp package bridges this gap by running an MCP server locally over stdio via npx, requiring zero persistent background infrastructure.
Tool Primitives and Blocking Timeouts
The server exposes eight core tools: create_email, wait_for_email, list_messages, read_message, list_emails, send_email, delete_message, and delete_email. The critical primitive is wait_for_email, which blocks for up to 90 seconds while polling the inbox. Crucially, if no email arrives before the limit expires, the tool returns a { status: 'timeout' } payload rather than throwing an exception. Returning expected waiting states as data prevents LLMs from hallucinating errors or abandoning the run prematurely.
Integration with Claude Code and Codex
For interactive workflows, developers can install the tool directly into Claude Code using claude mcp add moemail -e MOEMAIL_API_KEY=... -- npx -y @moemail/mcp. For automated continuous integration pipelines, the @moemail/cli package supports structured --json output and auto-detects skill installations for both Claude Code and Codex via moemail skill install.
Try it in 2 minutes
claude mcp add moemail -e MOEMAIL_API_KEY=mk_live_key -- npx -y @moemail/mcpbash
✓ When to use
- Automating end-to-end integration and staging tests for signup and password-reset flows.
- Running headless CI checks that require disposable account creation.
✕ When NOT to use
- Mass account registration or abusive free-tier farming against third-party platforms.
- Production transactional email delivery requiring permanent mailbox persistence.
What to do today
- Add the @moemail/mcp server to your Claude Code or Cursor configuration.
- Run moemail skill install to register the disposable inbox workflow in Codex or Claude Code.
- Refactor custom agent tools to return pending or timeout states as JSON objects instead of runtime exceptions.
Sources