mcpField
M
maildev-mcp

maildev-mcp

Local
github.com/pierre3Developer Tools2Updated 32w ago

About maildev-mcp

maildev-mcp lets an MCP client manage MailDev Docker containers and inspect received emails. It is intended for local development and automated email testing, including attachment verification.

Key features

  1. 01Start and stop MailDev containers
  2. 02List, search, and inspect emails
  3. 03Wait for matching incoming email
  4. 04Read HTML bodies and attachments
  5. 05Verify attachment bytes against source data

Use cases

  1. 01Check email output during local development
  2. 02Wait for asynchronous email delivery in tests
  3. 03Validate received attachment integrity

MCP support

This MCP server exposes tools to control MailDev containers and access their email contents through an MCP client.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
nugetMailDevMcp1.0.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

MailDevMcp

English | 日本語

CI NuGet

mcp-name: io.github.pierre3/maildev-mcp

An MCP (Model Context Protocol) server for MailDev.
Manage MailDev Docker containers and inspect received emails directly from your AI-powered editor or MCP client.

This server is intended for local development and test automation scenarios where an MCP client needs to:

  • start or stop a MailDev container
  • inspect inbox contents
  • wait for emails after triggering application behavior
  • inspect HTML bodies and attachments
  • verify attachment integrity byte-for-byte

Installation

Install as a global .NET tool:

dotnet tool install -g MailDevMcp

After installation, the maildev-mcp command becomes available.

MCP Client Configuration

Add the following to your MCP client settings (e.g. Claude Desktop, VS Code, etc.):

{
  "mcpServers": {
    "maildev-mcp": {
      "command": "maildev-mcp",
      "env": {
        "MAILDEV_API_PORT": "1080"
      }
    }
  }
}
Environment Variables
VariableDefaultDescription
MAILDEV_API_PORT1080Port number for the MailDev REST API

Typical Workflow

  1. Call StartMaildev to launch a local MailDev container
  2. Trigger your application to send an email
  3. Call WaitForEmail if delivery is asynchronous
  4. Use ListEmails, SearchEmails, or GetEmail to inspect the result
  5. Use GetEmailHtml, GetAttachmentContent, or VerifyAttachment when deeper validation is needed
  6. Clean up with DeleteEmail, DeleteAllEmails, or StopMaildev

Available Tools

ToolDescription
StartMaildevStart the MailDev Docker container with configurable SMTP port, API port, authentication, and TLS
StopMaildevStop and remove the MailDev Docker container
MaildevStatusCheck the running status of MailDev
ListEmailsRetrieve the list of received emails
GetEmailGet the details of an email by ID, including attachment information
GetEmailHtmlGet the HTML body of an email by ID
SearchEmailsSearch received emails by subject, sender, or recipient
DeleteEmailDelete a single email by ID
DeleteAllEmailsDelete all received emails
WaitForEmailWait until a new email matching given criteria arrives (useful for test automation)
GetAttachmentContentGet the raw Base64-encoded content of an email attachment
VerifyAttachmentVerify that an email attachment matches the original data by byte-by-byte comparison

Tool Behavior Notes

  • StartMaildev
    • Supports custom SMTP and API ports
    • Supports optional SMTP authentication
    • Treats empty or whitespace-only credentials as authentication disabled
    • Supports TLS with a generated self-signed certificate
  • GetEmail and ListEmails
    • Render missing or empty subjects as (no subject)
    • Render missing address lists as (none)
  • WaitForEmail
    • Polls MailDev until a matching email arrives or the timeout is reached
    • Reports transient MailDev connection failures in the returned message when they occur during polling
  • VerifyAttachment
    • Accepts a Base64-encoded original payload
    • Compares the received attachment byte-by-byte
    • Reports either exact match, size mismatch, or content mismatch

Requirements and Assumptions

  • Docker must be installed and available on the same machine where this MCP server runs
  • MailDev is accessed through its HTTP API on localhost
  • The configured API port in the MCP client must match the MailDev API port exposed by Docker

Prerequisites

Building from Source

git clone https://github.com/pierre3/MailDevMcp.git
cd MailDevMcp
dotnet pack -c Release
dotnet tool install -g --add-source ./bin/Release MailDevMcp

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.