A Gmail or FastMail connector is a better fit when you are on Gmail or FastMail. This is for the mailbox that has neither: speak the protocol the server already speaks, and the host does not have to have thought about integrations at all. The cost is the credential model that comes with IMAP — an account password in an environment variable rather than a scoped, revocable token — so prefer an app-specific password where your provider issues them.
A small server for browsing email over IMAP, built on fastmcp. IMAP is the one protocol nearly every mail server speaks, which makes this the option when the mailbox lives somewhere without a modern API — a self-hosted server, a corporate host, an old provider.
Browsing access to the mailbox the credentials belong to, over the protocol the server already exposes. Because the connection is plain IMAP rather than a vendor API, the same setup works against any host that speaks it — the only thing that changes between mailboxes is the three configured values.
An IMAP account and its password. Three values go in the `env` block of your client config: `IMAP_USER`, `IMAP_PASSWORD` and `IMAP_SERVER`, the last being the host's DNS name or IP address. Python with uv — the client entry runs the server script with `uv run` from your checkout, so the repository has to be cloned locally. The project is `imap-test` (0.1.0 in pyproject).
One command plus a key — uvx imap-test, then supply credentials