MCP server for sending SMTP email notifications
If you already use Email, the email mcp server is the piece that lets your assistant work with it directly. MCP server for sending SMTP email notifications.
An MCP (Model Context Protocol) server that exposes a send_email tool for SMTP notifications. This enables an "Agent -> SMTP server -> personal email -> phone notification" workflow.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
minimal — return counts and identifiers (messageId, counts, attempts)summary — return counts plus accepted/rejected lists (may be truncated)Variable — RequiredSMTP_URL — NoSMTP_HOST — Yes*SMTP_PORT — NoSMTP_SECURE — NoSMTP_USER — Yes*SMTP_PASS — Yes*SMTP_FROM — NoSMTP_TLS_REJECT_UNAUTHORIZED — NoSMTP_CONN_TIMEOUT — NoConfiguration is passed through the environment: SMTP_HOST, SMTP_PORT, SMTP_SECURE, SMTP_USER, SMTP_PASS, SMTP_FROM, SMTP_TLS_REJECT_UNAUTHORIZED, SMTP_CONN_TIMEOUT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as @agguy/email-sender-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Email's toolset — minimal, summary, Variable and 11 more — is a fair guide to whether it matches your workflow. It is maintained by agguy; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Email's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| minimal | return counts and identifiers (messageId, counts, attempts). |
| summary | return counts plus accepted/rejected lists (may be truncated). |
| Variable | Required |
| SMTP_URL | No |
| SMTP_HOST | Yes* |
| SMTP_PORT | No |
| SMTP_SECURE | No |
| SMTP_USER | Yes* |
| SMTP_PASS | Yes* |
| SMTP_FROM | No |
| SMTP_TLS_REJECT_UNAUTHORIZED | No |
| SMTP_CONN_TIMEOUT | No |
| SMTP_GREETING_TIMEOUT | No |
| SMTP_SOCKET_TIMEOUT | No |
### Recommended configuration
```json
{
"mcpServers": {
"email-sender": {
"command": "npx",
"args": ["-y", "--quiet", "@agguy/email-sender-mcp@latest"],
"env": {
"SMTP_HOST": "smtp.example.com",
"SMTP_PORT": "465",
"SMTP_SECURE": "true",
"SMTP_USER": "your-email@example.com",
"SMTP_PASS": "your-app-password",
"SMTP_FROM": "your-email@example.com"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SMTP_HOST | Endpoint or connection string the server talks to. | Optional |
| SMTP_PORT | Configuration value read at startup. | Optional |
| SMTP_SECURE | Configuration value read at startup. | Optional |
| SMTP_USER | Configuration value read at startup. | Optional |
| SMTP_PASS | Configuration value read at startup. | Optional |
| SMTP_FROM | Configuration value read at startup. | Optional |
| SMTP_TLS_REJECT_UNAUTHORIZED | Configuration value read at startup. | Optional |
| SMTP_CONN_TIMEOUT | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.