OpenInbox – Email for AI Agents
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@OpenInbox – Email for AI Agents Create a temp inbox, sign up for a trial at example.com, and confirm the account."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
OpenInbox MCP server
Give your AI agent its own email inbox. This Model Context Protocol server lets Claude, ChatGPT, Cursor and other MCP clients create real, disposable email addresses with OpenInbox, wait for incoming mail, and pull out verification codes and links, so the agent can finish signups, logins and email-flow tests without a human checking an inbox.
You: Sign up for the Acme newsletter and confirm the subscription.
Agent: create_inbox → k7x2@teminbox.click
(fills in the signup form)
get_verification → link: https://acme.com/confirm?t=…
(opens the link) → Done, subscription confirmed.Quick start
Get an API key. API access is included in the OpenInbox Pro, Business and 7-Day Pass plans (pricing). Copy your key from Settings → API.
Add the server to your client (examples below). Replace
tmp_your_keywith your key.
Claude Code
claude mcp add openinbox --env OPENINBOX_API_KEY=tmp_your_key -- npx -y openinbox-mcpClaude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"openinbox": {
"command": "npx",
"args": ["-y", "openinbox-mcp"],
"env": { "OPENINBOX_API_KEY": "tmp_your_key" }
}
}
}Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
{
"mcpServers": {
"openinbox": {
"command": "npx",
"args": ["-y", "openinbox-mcp"],
"env": { "OPENINBOX_API_KEY": "tmp_your_key" }
}
}
}VS Code (GitHub Copilot agent mode)
Add to .vscode/mcp.json:
{
"servers": {
"openinbox": {
"type": "stdio",
"command": "npx",
"args": ["-y", "openinbox-mcp"],
"env": { "OPENINBOX_API_KEY": "tmp_your_key" }
}
}
}Any other MCP client that can run a stdio server works the same way: command npx, args -y openinbox-mcp, env OPENINBOX_API_KEY.
Related MCP server: agent-inbox
Tools
Tool | What it does |
| Creates a new disposable address. Optional |
| Waits for the next email and returns just the one-time code and/or verification link. The shortcut for signups and logins. |
| Waits for a matching email ( |
| Lists emails in an inbox with previews and detected codes. |
| Reads one email as plain text, with its codes and links. |
| Lists your active inboxes. |
| Deletes an inbox when the task is done. |
| Shows your plan, remaining API requests today and inbox usage. |
Codes and links are detected server-side (6-digit codes, 123 456, alphanumeric codes, verify/confirm/magic-link/reset links, in many languages), so the agent doesn't need to parse HTML.
Example prompts
"Create a temporary email, sign up for a trial at example.com with it, and confirm the account."
"Test our password-reset flow on staging: request a reset for a fresh inbox and check that the email arrives with a working link."
"Make an inbox, register on the forum, and tell me the verification code."
Tips
Sites that block temp-mail domains: add your own domain in OpenInbox (included in Pro, Business and 7-Day Pass) and pass it as
domaintocreate_inbox. Addresses on your domain look like any normal mailbox.One inbox per site or task. Reuse it for follow-up emails, and delete it when you're done.
Inbox lifetime depends on your plan (Pro: 7 days, Business: 30 days, 7-Day Pass: 7 days).
Limits and fair use
Each API call counts toward your plan's daily request limit (3,000 on Pro and 7-Day Pass, 10,000 on Business). Inbox creation is also capped per hour (60 on Pro and 7-Day Pass, 300 on Business). wait_for_email and get_verification hold a single request open while waiting, so waiting costs about one request per minute.
Use it for your own accounts, testing and automation. Mass account creation, spam and other abuse are against the OpenInbox terms and lead to suspension.
Configuration
Variable | Required | Default |
| yes | none |
| no |
|
Development
npm install
npm test # builds and runs the test suite
npm run build # outputs dist/index.jsLinks
Website: openinbox.io
AI agents: openinbox.io/ai-agents
API docs: openinbox.io/api-docs
n8n integration: n8n-nodes-openinbox
Support: support@openinbox.io
License
MIT © OpenInbox
Available Tools
8 toolscreate_inboxCreate 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.
Inputs: domain, prefix.
delete_inboxDelete inboxADestructiveIdempotent
Delete an inbox and its emails when the task is done.
Inputs: inbox_id (required).
get_accountAccount and limitsARead-only
Show the user's OpenInbox plan, remaining API requests today and inbox usage.
Inputs: no named parameters.
get_verificationGet verification code or linkA
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.
Inputs: inbox_id (required), from, timeout_seconds.
list_emailsList emailsARead-only
List the emails in an inbox (newest first, up to 30) with sender, subject, preview and detected codes.
Inputs: inbox_id (required), unread_only.
list_inboxesList inboxesBRead-only
List the user's active OpenInbox inboxes.
Inputs: no named parameters.
read_emailRead emailARead-only
Read one email as plain text, with its detected codes and links.
Inputs: email_id (required).
wait_for_emailWait 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.
Inputs: inbox_id (required), from, since, subject, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.
Disposable inboxes for AI agents: create, wait for delivery, and extract email content or links.
Disposable email inboxes for AI agents — read messages and verification codes.
Real inboxes for AI agents: create an address, then wait for and read sign-up codes and magic links.
1
Related MCP Servers
- 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 disposable email inboxes for AI agents to automatically receive and extract OTPs and magic links, enabling seamless email verification during autonomous workflows.3121 npmMIT
- AlicenseAqualityCmaintenanceProvides AI agents with real email infrastructure, enabling them to create inboxes, send/receive messages, and extract verification codes from incoming mail.14MIT