maildev-mcp
mcpotherio.github.pierre3/maildev-mcp · v1.0.1
MailDev MCP server. Manage Docker containers and inspect emails from your AI editor or MCP client.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # maildev (io.github.pierre3/maildev-mcp), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-maildev.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec uvx mcp-proxy --host 127.0.0.1 --port 8101 --pass-environment -- dnx [email protected] --yes [Unit] Description=MCP server maildev (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/maildev WorkingDirectory=/var/lib/mcp/maildev ExecStart=/opt/mcp/my-agent/bin/maildev.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/maildev [Install] WantedBy=multi-user.target
connect to it
copy what your client needsdnx [email protected] --yes # env: MAILDEV_API_PORT
{
"mcpServers": {
"maildev": {
"command": "dnx",
"args": [
"[email protected]",
"--yes"
],
"env": {
"MAILDEV_API_PORT": "${MAILDEV_API_PORT}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add maildev -e "MAILDEV_API_PORT=${MAILDEV_API_PORT}" -- dnx [email protected] --yes
{
"mcpServers": {
"maildev": {
"command": "dnx",
"args": [
"[email protected]",
"--yes"
],
"env": {
"MAILDEV_API_PORT": "${MAILDEV_API_PORT}"
}
}
}
}
{
"servers": {
"maildev": {
"type": "stdio",
"command": "dnx",
"args": [
"[email protected]",
"--yes"
],
"env": {
"MAILDEV_API_PORT": "${MAILDEV_API_PORT}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.pierre3/maildev-mcp
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.