vs IMAP MCP server

Self-hosted IMAP,
or managed OAuth too.

"IMAP MCP server" is the catch-all for self-hosted connectors that speak IMAP/SMTP — anything from Gmail to ProtonMail Bridge to your own mail server. The OSS field (codefuturist/email-mcp, nikolausm, ai-zerolab, yunfeizhu) is pragmatic when you want one MCP for any inbox. CME covers the same IMAP surface AND adds managed OAuth for Gmail / M365 — no two integrations.

ConnectMyEmail

IMAP + OAuth, hosted.

App passwords for self-hosted mail; OAuth PKCE for Gmail and Microsoft 365 — same endpoint, same 195 tools.

IMAP MCP server

OSS, self-hosted, IMAP-only.

MIT-licensed Node/Python servers. codefuturist/email-mcp leads on features (47 tools, IMAP IDLE, multi-provider auto-detect).

Decision matrix

Which one is right for you?

Choose CME if…
  • You're on Gmail or Microsoft 365 and don't want to build OAuth flows yourself.
  • You want IMAP support PLUS modern OAuth in one connector.
  • You want depth: sender detection, newsletter detection, bulk unsubscribe, follow-ups, sweep 500K, audit log.
Choose IMAP MCP server if…
  • Your inbox is on a self-hosted or niche provider (mox, ProtonMail Bridge, corporate Exchange).
  • You're fine with app passwords / basic auth and trust your own secret handling.
  • You want to read the source, audit it, fork it, run it locally.
Choose both if…
  • Mixed estate: some IMAP-only mailboxes, some OAuth-managed.
  • Prototype with OSS locally and graduate to CME for production reliability.
Feature-by-feature

17 rows. Every cell sourced.

Connection model

Auth and hosting.
Hosting
CME
Hosted, stateless
IMAP MCP server
Self-host (Docker, npm, pip)
Auth model
CME
OAuth PKCE + IMAP
IMAP MCP server
App password / basic auth (most); OAuth2 experimental in codefuturist
Setup time
CME
Minutes via OAuth
IMAP MCP server
Hours (OAuth client + IMAP + hosting + secrets)

Tool surface

Coverage and depth.
Tool count
CME
195
IMAP MCP server
codefuturist 47; others 10-20
Providers
CME
Gmail, Outlook + IMAP universal
IMAP MCP server
codefuturist auto-detects 8 providers; others single
Sweep / bulk ops
CME
500K in <45s
IMAP MCP server
Per-folder batch only
Sender / newsletter detection
CME
IMAP MCP server
Bulk unsubscribe
CME
IMAP MCP server
Real-time push
CME
yes (webhooks)
IMAP MCP server
codefuturist IDLE; others polling
Attachment handling
CME
IMAP MCP server
yes (codefuturist 5MB cap)

Operational

Maintenance and ops.
Multi-account
CME
IMAP MCP server
codefuturist + nikolausm yes; many single
Encryption at rest
CME
Vendor-managed (AES-256-GCM)
IMAP MCP server
nikolausm AES-256; others vary
Maintenance / support
CME
Vendor-maintained, tiered support
IMAP MCP server
GitHub issues, single-maintainer risk

Pricing

License vs total cost.
Software license
CME
$0 Free
IMAP MCP server
$0 (MIT)
Hosting cost
CME
Included
IMAP MCP server
Your VPS / container
Ops time
CME
Included
IMAP MCP server
OAuth + IMAP + monitoring + patching
Entry paid
CME
$9/mo
IMAP MCP server
n/a (DIY)
Pricing

Side by side.

OSS IMAP servers are MIT-licensed and free. Real cost is hosting plus engineer-hours wiring OAuth, rotating app passwords, monitoring IDLE connections.
ConnectMyEmail
  • Free1 inbox, 5K cleanup actions/mo
    $0
  • Pro3 inboxes, 25K cleanup actions/mo
    $9/mo
  • Power10 inboxes, 100K cleanup actions/mo
    $25/mo
IMAP MCP server
  • OSS licenseMIT — codefuturist, nikolausm, ai-zerolab
    $0
  • HostingVPS, secrets store, monitoring
    Your infra
  • Ops timeOAuth client, IMAP creds, patching
    Engineer hours

OSS is great for tinkerers and self-hosted mailboxes. CME is for people who want IMAP + OAuth providers + email depth in one managed endpoint.

Plug your real inbox in.

Free tier ships read-only access. No credit card. Connect Gmail, Outlook, iCloud, or any IMAP account in under a minute.