Mcp

EmailMCP

AI agent email — 23 tools free to read inbox, 28 paid to send. $9.99/mo. Token auto-provisioned.

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use EmailMCP

Choose if

You want a single MCP that handles both inbox reads (IMAP IDLE watching, filtering, rule engines) and outbound sends (templated, attachments, multi-provider) from inside an agent loop. The free read tier is generous (23 tools) — pair with the $9.99/mo send tier only if outbound matters. The autonomous-VPS mode is unusual: it provisions a $2.50–$4/mo VPS so the agent owns the sending domain end-to-end with DKIM/SPF/DMARC.

Avoid if

You need OAuth-based Gmail/Outlook access, mailbox-on-behalf-of delegation, or strong compliance posture (HIPAA, SOC2 attestation). EmailMCP relies on app-specific passwords / provider API keys in the host's environment — fine for indie developers, weaker for team-shared mailboxes. Also avoid if you need a documented per-tool rate limit before you wire the send path into automated flows.

Risk Flags

  • MEDIUM cost Read tools (23) are free; send tools (28) are gated behind a $9.99/month subscription. Agents that mix read + send must keep a token attached for the send path.
  • MEDIUM auth IMAP path requires email + app-specific password stored in env vars; SMTP/provider mode requires per-provider API keys (Mailgun, SendGrid, AWS SES, etc.). No OAuth flow — secrets sit at the MCP host's environment.
  • MEDIUM rate_limit README exposes `RATE_LIMIT_HOURLY` and `RATE_LIMIT_DAILY` env vars but documents no specific numbers. Agents running batch sends should set these explicitly.
  • LOW maturity Solo-developer MIT-licensed project (nfodor/emailmcp). Test coverage cited as "1266 tests"; no production SLA disclosed.

Cost

Type: Freemium

Distribution

MCP Registry
io.setip/emailmcp
Repository
https://github.com/nfodor/emailmcp