OpenInbox – Email for AI Agents
OfficialRelated Servers
Alternatives to OpenInbox – Email for AI Agents
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceEnables AI coding agents to create disposable test inboxes, wait for and read incoming email, and extract confirmation links and one-time codes for sign-up, password-reset, and magic-link flows.612 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create disposable email inboxes and automatically extract OTPs, magic links, and verification codes from incoming emails.10 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to create temporary email addresses, receive confirmation emails, and extract verification links, automating sign-up and email verification workflows without manual intervention.621 npm64MIT
- AlicenseAqualityCmaintenanceProvides AI agents with real email infrastructure, enabling them to create inboxes, send/receive messages, and extract verification codes from incoming mail.14MIT
- AlicenseAqualityCmaintenanceProvides disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.3121 npmMIT

tmailor-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to create receive-only temporary email addresses and wait for incoming mail, returning one-time codes, verification links and plain text bodies so agents can complete sign-ups and confirmations. It also lists and reads messages, manages mailboxes and reports remaining quota.879 PyPI1MIT
TDQS
Scored across 8 tools
Each tool maps to a distinct resource-action (inbox CRUD vs. email retrieval vs. account info), but retrieval tools overlap: get_verification, wait_for_email, list_emails and read_email all return email content with codes and links, differing only in wait behavior and verbosity. The descriptions do a good job disambiguating when to use which, keeping this above average but not perfectly clean.
All names follow a snake_case verb_noun pattern (create_inbox, list_emails, delete_inbox, get_account), which is predictable and readable. Minor deviation: get_verification names an artifact rather than the resource object (email) used elsewhere, a small inconsistency in what the noun refers to.
Eight tools is well within the sweet spot and each has a clear job: inbox lifecycle (create/list/delete), email retrieval (list/read/wait/verify), and account introspection. Nothing feels padded or missing at the count level.
Core lifecycle for disposable inboxes is covered: create, list, receive/wait, read, and delete, plus account/quota visibility. Minor gaps like marking emails read/unread or deleting/searching individual emails are absent, but agents can work around them with the existing surface.