# Mail for Bots

> Mail for Bots gives AI agents and assistants (Claude, ChatGPT, Gemini, Cursor and any MCP client) their own real email inboxes. An agent can create an address, sign up to services, read verification codes, send email, wait for replies and follow up, without access to the user's personal inbox. Hosted MCP server, REST API, webhooks and custom domains. Free plan: 3 inboxes and 50 emails a day. Pro: $20/month, 100 inboxes, 5,000 emails a day.

## Start here
- [Email for AI agents](https://mailforbots.com/email-for-ai-agents.md): why agents need their own inbox and what they can do with it
- [MCP email server](https://mailforbots.com/mcp-email-server.md): connect Claude, ChatGPT (Codex), Gemini, Cursor, VS Code or Windsurf in one step
- [Email testing for developers](https://mailforbots.com/email-testing-for-developers.md): disposable inboxes for sign-up and password-reset tests
- [Pricing](https://mailforbots.com/pricing.md): Free and Pro plans
- [FAQ](https://mailforbots.com/faq.md)

## Connect
- MCP endpoint (Streamable HTTP): https://mailforbots.com/mcp, authenticated with an API key as a bearer token (`Authorization: Bearer bm_...`)
- REST API base: https://mailforbots.com/api/v1 (reference: https://mailforbots.com/docs/rest)
- Indexes: [Blog](https://mailforbots.com/blog.md), [Comparisons](https://mailforbots.com/compare.md)

## Articles
- [How to QA email flows in 2026 with AI](https://mailforbots.com/blog/how-to-qa-email-flows-with-ai-2026.md): A practical guide to testing sign-up, password-reset and magic-link emails in 2026: real inboxes per test, waiting instead of sleeping, and letting an AI agent run the checks.
- [How to let an AI agent sign up for a website and read the verification email](https://mailforbots.com/blog/let-ai-agent-sign-up-for-websites.md): Give Claude, ChatGPT or Cursor its own inbox so it can register, wait for the confirmation email and read the code or link itself. Step by step, with MCP.
- [How to test password-reset emails in CI](https://mailforbots.com/blog/test-password-reset-emails-in-ci.md): Test real password-reset and verification emails in CI: create a fresh inbox per run, wait for the message, extract the link and assert on it. Playwright example included.
- [How to require human approval before an AI agent sends email](https://mailforbots.com/blog/human-approval-for-ai-agent-email.md): Four controls that keep an email-capable AI agent safe: drafts that wait for approval, read-only keys, inbox-scoped keys and daily sending limits.
- [AI agents and email verification codes: how to handle OTPs safely](https://mailforbots.com/blog/ai-agents-email-otp-verification-codes.md): Why agents stall at 'check your email for a code', how extracted codes and links solve it, and how to treat inbound email as untrusted input.
- [Best email for AI agents in 2026: what to look for and the options](https://mailforbots.com/blog/best-email-for-ai-agents-2026.md): A fair look at the ways to give an AI agent email in 2026: agent-native inbox APIs, QA testing tools, sender APIs and self-hosted capture, and which fits which job.
- [Give Claude Code its own email inbox with one MCP command](https://mailforbots.com/blog/claude-code-email-mcp.md): Add a hosted email MCP server to Claude Code with one command. It gets its own inbox, waits for verification mail, drafts replies, and never touches your Gmail.
- [Email MCP setup for Cursor, Codex CLI and Gemini CLI](https://mailforbots.com/blog/cursor-codex-gemini-email-mcp-setup.md): Add a hosted email MCP server to Cursor, Codex CLI or Gemini CLI with one URL and a bearer key. Copy-paste configs, a test run, and the OAuth limit.
- [Playwright email tests: OTP and magic links with a per-worker inbox fixture](https://mailforbots.com/blog/playwright-email-verification-otp-tests.md): Create one throwaway inbox per Playwright worker, submit its address, and wait for the OTP or magic link over REST instead of sleep(). Fixture code included.
- [Email 2FA in browser agents: Playwright MCP and Browser Use](https://mailforbots.com/blog/agent-signup-2fa-browser-automation.md): How a browser agent gets past "enter the code we emailed you": give it its own inbox and a blocking wait tool, and pair it with Playwright MCP.
- [Prompt injection in email: how to let an AI agent read it safely](https://mailforbots.com/blog/read-email-safely-prompt-injection-agents.md): Treat every inbound email as untrusted. How to let an AI agent read mail safely: scoped API keys, draft-only sending, a dedicated inbox and header checks.
- [Gmail MCP vs a dedicated agent inbox: which should an AI agent use?](https://mailforbots.com/blog/gmail-mcp-vs-dedicated-agent-inbox.md): Gmail MCP server or a dedicated agent inbox? Compare OAuth blast radius, signup and OTP use, audit trail, sending identity and revocation, with setup steps.
- [What is an agent inbox? Definition and how it differs from a sender API](https://mailforbots.com/blog/what-is-an-agent-inbox.md): An agent inbox is a real email address an AI agent owns through an API or MCP server. See how it differs from Gmail, sender APIs and temp mail, and what to look for.
- [How to test sign-up and magic-link emails in Cypress](https://mailforbots.com/blog/cypress-email-verification-tests.md): Test email verification in Cypress with a throwaway inbox: create it with cy.request, wait for the code or magic link, and avoid timeouts. Commands included.
- [How to give an n8n AI agent its own email inbox](https://mailforbots.com/blog/n8n-ai-agent-email-inbox.md): Trigger n8n workflows from incoming email with a Webhook node, then read, reply or draft with HTTP Request nodes. Step-by-step setup with node JSON.
- [How to give a LangChain or LangGraph agent an email inbox](https://mailforbots.com/blog/langchain-agent-email-tool.md): Give a LangChain.js or LangGraph agent its own inbox with three tool() functions: create an inbox, wait for mail, and draft replies for human approval.

## Comparisons
- [A Mailosaur alternative for AI-era email testing](https://mailforbots.com/compare/mailosaur-alternative.md): Comparing Mail for Bots and Mailosaur for email testing: free tier, inboxes per plan, MCP for AI agents, drafts, and when Mailosaur is still the better pick.
- [A MailSlurp alternative with a simple inbox for agents and QA](https://mailforbots.com/compare/mailslurp-alternative.md): Comparing Mail for Bots and MailSlurp: what each covers for AI agents and email testing, and when MailSlurp's larger toolbox is worth it.
- [An AgentMail alternative: Mail for Bots vs AgentMail](https://mailforbots.com/compare/agentmail-alternative.md): A transparent head-to-head of Mail for Bots and AgentMail for AI agent email: plans, inboxes, MCP, approvals, custom domains and who each is for.
- [A Mailinator alternative for private, AI-ready test inboxes](https://mailforbots.com/compare/mailinator-alternative.md): Public inboxes are fine until a test touches real data. Compare Mailinator with private inboxes from Mail for Bots, with MCP and an API for AI agents.
- [Mailpit alternative: when you need a real, hosted inbox](https://mailforbots.com/compare/mailpit-alternative.md): Mailpit is great for local SMTP capture. Here is when a hosted inbox that receives real internet email, like Mail for Bots, is the better tool.
- [Best email MCP servers in 2026, sorted by job](https://mailforbots.com/compare/best-email-mcp-servers-2026.md): The best email MCP server depends on the job: a mailbox wrapper, a sending API, a QA inbox or a dedicated agent inbox. Comparison from public vendor pages, updated October 2026.

## Documentation
- [Quickstart](https://mailforbots.com/docs/quickstart.md): Create an account, make an API key and connect Claude, ChatGPT, Gemini, Cursor or any MCP client to your own AI email inbox in two minutes.
- [API keys and scopes](https://mailforbots.com/docs/keys.md): How Mail for Bots API keys work: scopes, inbox-restricted keys and how to limit what an AI agent can do with email.
- [MCP tools](https://mailforbots.com/docs/mcp.md): Every email tool the Mail for Bots MCP server gives an AI agent: create inboxes, wait for email, read codes, send, reply and more.
- [REST API](https://mailforbots.com/docs/rest.md): The Mail for Bots REST API reference for inboxes, messages, threads, drafts, webhooks and domains, with curl examples.
- [Search operators](https://mailforbots.com/docs/search.md): Gmail-style search operators for finding email by sender, subject, label, date and attachment in an AI agent's inbox.
- [Plus-addressing](https://mailforbots.com/docs/plus-addressing.md): Use one inbox for many sign-ups with name+tag addresses that all land in the same Mail for Bots inbox.
- [Custom domains](https://mailforbots.com/docs/domains.md): Send and receive AI agent email from your own domain with Mail for Bots: DNS records, DKIM and verification.
- [Webhooks](https://mailforbots.com/docs/webhooks.md): Get notified the moment an email arrives or is sent. Signed webhooks for your own apps and agents.
- [Email analytics](https://mailforbots.com/docs/analytics.md): Delivery, bounce and open tracking for email your AI agents send.
- [Teams](https://mailforbots.com/docs/teams.md): Share inboxes, API keys and billing across a team with Mail for Bots.
- [Limits and quotas](https://mailforbots.com/docs/limits.md): Inbox, sending and recipient limits on the Free and Pro plans, and what happens when an agent reaches them.
- [Errors](https://mailforbots.com/docs/errors.md): Error codes and messages from the Mail for Bots API and MCP server, and how to fix them.

## Optional
- [Terms of Service](https://mailforbots.com/terms.md)
- [Privacy Policy](https://mailforbots.com/privacy.md)
- [Acceptable Use Policy](https://mailforbots.com/acceptable-use.md)