io.github.pierre3/maildev-mcp MCP Server
io.github.pierre3/maildev-mcp
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.pierre3/maildev-mcp MCP server?
MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client.
How to install io.github.pierre3/maildev-mcp
Copy-paste configuration for popular MCP clients.
MAILDEV_API_PORTPort number for the MailDev REST API (default: 1080)
{
"mcpServers": {
"maildev-mcp": {
"command": "dnx",
"args": [
"MailDevMcp"
],
"env": {
"MAILDEV_API_PORT": "<YOUR_MAILDEV_API_PORT>"
}
}
}
}Related MCP servers

OWASP ZAP MCP Server
MCP server for OWASP ZAP vulnerability scanning with Docker management
Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP.
Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP.

Supervise a local dev stack — databases, brokers and services declared in an Alphasfile — over MCP.

Feynman's twelve-problems method as an MCP server: dormant problems + an evoke loop for new tricks.

PieterPost MCP
Let AI agents prepare, review, pay for, and send real letters and postcards.
