Enterprise DNA
M MCP Servers Developer low

marlinjai/email-mcp

by Various

Unified MCP server for email access across Gmail, Outlook, iCloud, and IMAP

M

MCP

marlinjai/email-mcp

Added 1 June 2026

Overview

A TypeScript-based Model Context Protocol server that provides a unified interface for email access across Gmail, Outlook, iCloud, and IMAP. It allows AI agents to interact with multiple email providers through a single MCP endpoint.

Best for

Best for
Developers prototyping MCP-based email agents who need a unified abstraction

Use cases

  • Connecting AI assistants to read and send emails from multiple providers
  • Automating email-based workflows like triage or filtering
  • Integrating email functionality into MCP-compatible agent frameworks

Notes

A TypeScript-based Model Context Protocol server that provides a unified interface for email access across Gmail, Outlook, iCloud, and IMAP. It allows AI agents to interact with multiple email providers through a single MCP endpoint.

13 stars on GitHub. Last updated 2026-03-16. Licensed MIT.

Use cases

  • Connecting AI assistants to read and send emails from multiple providers
  • Automating email-based workflows like triage or filtering
  • Integrating email functionality into MCP-compatible agent frameworks

Pros

  • Single API for multiple email backends reduces integration effort
  • Written in TypeScript for type safety and broad ecosystem compatibility
  • Open source with permissive license for customization

Cons

  • Very early project (13 stars) with minimal community or documentation
  • No clear testing or security audit for production use
  • Relies on third-party IMAP/OAuth configurations which can be complex

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Single API for multiple email backends reduces integration effort
  • Written in TypeScript for type safety and broad ecosystem compatibility
  • Open source with permissive license for customization

Cons

  • Very early project (13 stars) with minimal community or documentation
  • No clear testing or security audit for production use
  • Relies on third-party IMAP/OAuth configurations which can be complex