Supported email providers
Which email providers you can connect to inboxmcp: over OAuth, from the portal presets, or with server details you enter yourself.
inboxmcp connects to your existing mailbox — we don’t host mail ourselves. The three sections below show which providers we support and how:
- SaaS providers with their own OAuth integration (one click in the portal, no app password)
- Presets that are directly selectable in the portal (server data is filled in for you)
- Other providers you can wire up via “Other” with the server details listed here
1. SaaS providers (OAuth)
These providers authenticate via their own login screen — no app password, no server config. The refresh token is stored encrypted on our side; if you revoke access from the provider account, the connection is severed on our side immediately.
| Provider | Connection | Status |
|---|---|---|
| Microsoft 365 | OAuth | Available |
| Google Workspace | OAuth | In review |
| Proton Mail | OAuth | In review |
Setup guide for M365: Connect Microsoft 365.
2. Portal presets
In the mailbox dialog of the portal you’ll find these providers as clickable presets — server, port and encryption are filled in automatically. You only enter email address and password.
| Provider | IMAP | SMTP | Note |
|---|---|---|---|
| mailbox.org | imap.mailbox.org:993 (SSL) |
smtp.mailbox.org:587 (STARTTLS) |
— |
| Posteo | posteo.de:993 (SSL) |
posteo.de:587 (STARTTLS) |
— |
| IONOS | imap.ionos.de:993 (SSL) |
smtp.ionos.de:587 (STARTTLS) |
— |
| STRATO | imap.strato.de:993 (SSL) |
smtp.strato.de:465 (SSL) |
— |
| GMX | imap.gmx.net:993 (SSL) |
mail.gmx.net:587 (STARTTLS) |
— |
| web.de | imap.web.de:993 (SSL) |
smtp.web.de:587 (STARTTLS) |
— |
| SERGO Plesk hosting | plesk.sergo.cloud:993 (SSL) |
plesk.sergo.cloud:587 (STARTTLS) |
For mailboxes on SERGO web hosting |
3. Other providers
These providers don’t ship as portal presets, but they work fine via “Other”. Enter the server name and port as listed.
| Provider | IMAP | SMTP | Note |
|---|---|---|---|
| Apple iCloud Mail | imap.mail.me.com:993 (SSL) |
smtp.mail.me.com:587 (STARTTLS) |
Generate an app-specific password in the Apple ID settings |
| Yahoo Mail | imap.mail.yahoo.com:993 (SSL) |
smtp.mail.yahoo.com:587 (STARTTLS) |
Requires an app password from the Yahoo account settings |
| AOL Mail | imap.aol.com:993 (SSL) |
smtp.aol.com:587 (STARTTLS) |
Requires an app password from the AOL account settings |
| Fastmail | imap.fastmail.com:993 (SSL) |
smtp.fastmail.com:465 (SSL) |
Generate an app password in the Fastmail settings |
| Migadu | imap.migadu.com:993 (SSL) |
smtp.migadu.com:465 (SSL) |
— |
| Zoho Mail (EU) | imap.zoho.eu:993 (SSL) |
smtp.zoho.eu:587 (STARTTLS) |
App password required; US tenants use .com instead of .eu |
| Yandex Mail | imap.yandex.com:993 (SSL) |
smtp.yandex.com:587 (STARTTLS) |
Generate an app password in your Yandex ID |
| 1&1 / IONOS Mail | imap.1und1.de:993 (SSL) |
smtp.1und1.de:587 (STARTTLS) |
Same as the IONOS preset for newer accounts |
| T-Online | secureimap.t-online.de:993 (SSL) |
securesmtp.t-online.de:465 (SSL) |
Mail password is separate from the Telekom login |
| Hostpoint (CH) | asmtp.mail.hostpoint.ch:993 (SSL) |
asmtp.mail.hostpoint.ch:587 (STARTTLS) |
— |
| Cyon (CH) | mail.cyon.ch:993 (SSL) |
mail.cyon.ch:587 (STARTTLS) |
— |
| Bluewin / Swisscom | imap.bluewin.ch:993 (SSL) |
smtpauths.bluewin.ch:465 (SSL) |
Generate the mail password through the Swisscom login |
Don’t see your provider? Any mail server that speaks IMAP + SMTP over SSL/TLS or STARTTLS works — Plesk shared-hosting, your own Dovecot, self-hosted Stalwart, anything. The exact server data is in your provider’s documentation; usually under “IMAP” or “email client setup”.
If a provider is consistently missing, send us the suggestion at support@inboxmcp.io — if the server data is stable, we’ll ship it as a portal preset.
Notes
- App passwords: Several providers (Apple, Yahoo, Fastmail, Zoho, AOL, Yandex) don’t accept your regular login password for IMAP/SMTP — you have to generate a separate app password in the account settings. That’s a security measure on the provider’s side; inboxmcp stores this app password encrypted the same way it stores any other (Security & privacy).
- Proton Mail: Direct connection officially only works via the local Proton Mail Bridge running on your device — not reachable from a hosted service like inboxmcp. We’re evaluating the OAuth integration instead (see section 1).
- Tutanota: Uses a proprietary, end-to-end-encrypted protocol and does not support standard IMAP/SMTP. Connecting through inboxmcp is therefore not possible today.