OpenInbox – Email for AI Agents
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENINBOX_API_KEY | Yes | Your OpenInbox API key. Required. Copy it from Settings → API (API access is included in the Pro, Business and 7-Day Pass plans). | |
| OPENINBOX_API_URL | No | Base URL of the OpenInbox API. Optional. | https://api.openinbox.io/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
OpenInbox gives you real, disposable email addresses. Typical flow for signing up somewhere or testing an email flow:
create_inbox → use the returned address in the form.
Submit the form.
get_verification (or wait_for_email) → returns the one-time code and/or the verification link. Use one inbox per site/task, reuse it for follow-up emails, and delete_inbox when done. Inboxes expire automatically (lifetime depends on the user's plan).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_inboxA | Create a new disposable email address that can receive email right away. Use it to sign up for a website, receive a verification code or link, or test an email flow. Returns the address and an inbox_id for the other tools. |
| get_verificationA | Wait for the next verification email in an inbox and return just the one-time code and/or the verification / magic / password-reset link. The fastest way to finish a signup or login. Waits up to timeout_seconds for the email to arrive. |
| wait_for_emailA | Wait until a matching email arrives in an inbox and return it in full (text, detected codes, links). Without "since", returns the newest unread matching email, so repeated calls return successive emails. |
| list_emailsA | List the emails in an inbox (newest first, up to 30) with sender, subject, preview and detected codes. |
| read_emailA | Read one email as plain text, with its detected codes and links. |
| list_inboxesB | List the user's active OpenInbox inboxes. |
| delete_inboxA | Delete an inbox and its emails when the task is done. |
| get_accountA | Show the user's OpenInbox plan, remaining API requests today and inbox usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.