Most mail integrations bind you to one provider's SDK and one provider's OAuth dance. This one speaks IMAP and SMTP, so it works against whatever server you already have, and the setup is a five-line file. The cost of that simplicity is that a working password sits on disk in plain text — which is exactly why the Gmail path is documented as an app-specific password you can revoke on its own.
An MCP server that connects one ordinary mail account over IMAP and SMTP. It runs on your machine, reads its credentials from a local `.env` file, and talks directly to your provider — Gmail in the worked example, but anything speaking those two protocols will do.
- Mailbox search by date range and keyword, including the sent folder
- Daily counts of received mail, so "how much came in last week" is one question rather than a scroll
- Full message content with threading, addressed by email ID
- Composing and sending with CC recipients, over TLS
- A confirmation step before anything leaves: the message details are shown back to you first
Python 3.12 or higher and `uv` for the virtual environment; the package is `email_client` and the launcher command is `email-client`. A `.env` file holds `EMAIL_ADDRESS`, `EMAIL_PASSWORD`, `IMAP_SERVER`, `SMTP_SERVER` and `SMTP_PORT`. On Gmail that means two-step verification switched on and an app-specific password rather than your account password. Activity is logged to `email_client.log`.
One command plus a key — uvx email_client, then supply credentials