Email Automation MCP

What email-automation-mcp does

The email-automation-mcp MCP server gives an MCP client a set of email operations backed by standard SMTP and IMAP protocols. It is intended for workflows where an assistant needs to send or inspect email, rather than only generate message text.

Supported actions include sending email, reading an inbox, searching messages, creating drafts, and listing mail folders. The README identifies Gmail, Outlook, Yahoo, and Fastmail as supported providers, while also stating that standard email providers can be used. The server is therefore a fit for mailbox automation that can work through ordinary SMTP and IMAP access.

How it works

The email-automation-mcp MCP server runs locally and communicates with the MCP client over stdio. A client exposes the server's email operations to an assistant, which can then request actions such as send_email, read_inbox, or search_emails.

The email connection layer uses SMTP for sending and IMAP for mailbox access. The supplied material does not specify the individual connection fields, authentication methods, or provider-specific settings required for an account, so those details should be checked in the linked documentation before deployment.

Setup and configuration

The project can be installed from PyPI with:

pip install email_automation_mcp

The README also documents this stdio configuration for Claude Desktop and other MCP client configuration files:

{
  "mcpServers": {
    "email-automation-mcp": {
      "command": "uvx",
      "args": ["email-automation-mcp"]
    }
  }
}

As an alternative, install the package with pip and run the email-automation-mcp command. The README does not provide environment variable names or account credentials, so they should not be inferred from the installation example.

Tools and capabilities

The documented email-automation-mcp capabilities are:

• Send email through SMTP.
• Read messages from an inbox through IMAP.
• Search email.
• Create drafts.
• List mailbox folders.

The examples specifically refer to send_email, read_inbox, and search_emails. The README describes the other capabilities but does not provide their exact tool names or argument schemas.

Limitations and notes

The available material does not describe attachment handling, HTML formatting, reply or forwarding behavior, pagination, filtering syntax, or mailbox write operations beyond draft creation. It also does not list provider-specific setup instructions or credential fields. Confirm those details in the project's full documentation before relying on them in an automated workflow.

The repository states that the project is MIT licensed. Its README also advertises separate paid MEOK governance and enterprise offerings; those offerings are not required by the documented local installation of this email server.

Getting started with this email-automation-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.