# eMailPlane

> eMailPlane is software you install on your own Linux server that lets your app, your AI agents and your team send, receive and reply to email on your own domain (for example support@acme.com). Your code uses a REST API and signed webhooks, AI agents use an MCP server, and people use Outlook, Apple Mail, Thunderbird or a phone. Mailboxes, messages and signing keys are stored on your server. The service is in an invite-only beta.

Facts, limited to what is built today:

- A reply is threaded to the message it answers. Your app can read the whole conversation (`GET /v1/inbound/threads/:id`) and answer in the same thread (`POST /v1/emails` with `in_reply_to`).
- When mail arrives, a registered webhook receives a signed `message.received` event that carries only the message and thread ids, so message content never leaves your server inside a webhook.
- AI agents connect over MCP. They can send, read the conversation, wait for an answer in one call (`wait_for_reply`, up to 50 seconds per call) and reply. Each agent connection gets only the scopes you choose; agents never get admin access.
- People connect any mail app with a normal email login (IMAP).
- eMailPlane creates the DNS records a domain needs for email and checks each one against live DNS. A failed check shows the value it expected next to the value it found. Existing SPF entries are kept, and DMARC starts in report-only mode.
- Guardrails are on from day one: addresses that bounced, complained or unsubscribed are never mailed again; a key whose bounce or complaint rate climbs is slowed or paused automatically; a new key's daily sending grows gradually; incoming mail is virus-scanned, and infected mail is hidden from agents by default.
- Addresses and incoming mail are not counted on any plan. Plans are priced by the domains you add, the people who log in from a mail app, and the email you send. Billing is not live yet: during the invite-only beta no card is needed to set up and test.
- eMailPlane does not claim to be injection-proof. Treat the text of every email as untrusted input in an agent's prompt.
- Contact: hello@emailplane.com. Beta invites: https://emailplane.com/invite/

## Add email to my app

- [Developer quickstart](https://emailplane.com/developers/index.html.md): API calls, request and response shapes, the error envelope, and the status of each capability
- [Send an email](https://emailplane.com/developers/index.html.md#send-an-email): `POST /v1/emails` with an `Idempotency-Key` header; `202` means queued
- [Overview](https://emailplane.com/index.html.md): what eMailPlane does, in the words of the homepage

## Email for AI agents

- [MCP setup](https://emailplane.com/developers/mcp/index.html.md): the 41 tools, including `wait_for_reply`, and how an agent connects
- [Capability status](https://emailplane.com/developers/index.html.md#status): what is in the beta today and what is coming

## Install on my server

- [Beta access](https://emailplane.com/invite/index.html.md): the beta is invite-only; during the beta, setup on your server is done together with the eMailPlane team

## MCP

- [MCP setup](https://emailplane.com/developers/mcp/index.html.md): stdio configuration in the beta, and the planned remote endpoint `https://mail.<your-domain>/mcp`
- [MCP Registry entry (draft)](https://emailplane.com/mcp/server.json): `com.emailplane/mail`, remote URL template `https://mail.{domain}/mcp`; not yet published

## Pricing

- [Pricing](https://emailplane.com/pricing/index.html.md): Starter $19, Team $49, Growth $149 and Scale $399 a month, or $182, $470, $1,430 and $3,830 a year; addresses and incoming mail unlimited; invite-only beta, billing not live yet

## Security

- [Security and privacy](https://emailplane.com/security/index.html.md): the privacy statement, how data is stored, the prompt-injection position, service providers and vulnerability reporting
- [security.txt](https://emailplane.com/.well-known/security.txt): vulnerability contact

## Optional

- [Full text of this site](https://emailplane.com/llms-full.txt): every page above in one Markdown file