Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SMTP_HOST, SMTP_PORT, SMTP_TLS, SMTP_USER, SMTP_PASSWORD, SMTP_FROM, SMTP_REPLY_TO, SMTP_ALLOW_SEND, SMTP_ALLOWED_RECIPIENTS, SMTP_MAX_RECIPIENTS, SMTP_MAX_SENDS_PER_HOUR, SMTP_MAX_MESSAGE_BYTES, SMTP_MAX_ATTACHMENT_BYTES, SMTP_ATTACHMENT_DIR, SMTP_ATTACHMENT_TYPES, SMTP_SIGNATURE, SMTP_AUDIT_LOG, SMTP_ALLOW_TOOLS, SMTP_DENY_TOOLS, SMTP_INSECURE_TLSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"smtp": {
"command": "npx",
"args": [
"-y",
"@ni-c/smtp-mcp"
],
"env": {
"SMTP_HOST": "your-value",
"SMTP_PORT": "your-value",
"SMTP_TLS": "your-value",
"SMTP_USER": "your-value",
"SMTP_PASSWORD": "your-value",
"SMTP_FROM": "your-value",
"SMTP_REPLY_TO": "your-value",
"SMTP_ALLOW_SEND": "your-value",
"SMTP_ALLOWED_RECIPIENTS": "your-value",
"SMTP_MAX_RECIPIENTS": "your-value",
"SMTP_MAX_SENDS_PER_HOUR": "your-value",
"SMTP_MAX_MESSAGE_BYTES": "your-value",
"SMTP_MAX_ATTACHMENT_BYTES": "your-value",
"SMTP_ATTACHMENT_DIR": "your-value",
"SMTP_ATTACHMENT_TYPES": "your-value",
"SMTP_SIGNATURE": "your-value",
"SMTP_AUDIT_LOG": "your-value",
"SMTP_ALLOW_TOOLS": "your-value",
"SMTP_DENY_TOOLS": "your-value",
"SMTP_INSECURE_TLS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add smtp --env SMTP_HOST=your-value --env SMTP_PORT=your-value --env SMTP_TLS=your-value --env SMTP_USER=your-value --env SMTP_PASSWORD=your-value --env SMTP_FROM=your-value --env SMTP_REPLY_TO=your-value --env SMTP_ALLOW_SEND=your-value --env SMTP_ALLOWED_RECIPIENTS=your-value --env SMTP_MAX_RECIPIENTS=your-value --env SMTP_MAX_SENDS_PER_HOUR=your-value --env SMTP_MAX_MESSAGE_BYTES=your-value --env SMTP_MAX_ATTACHMENT_BYTES=your-value --env SMTP_ATTACHMENT_DIR=your-value --env SMTP_ATTACHMENT_TYPES=your-value --env SMTP_SIGNATURE=your-value --env SMTP_AUDIT_LOG=your-value --env SMTP_ALLOW_TOOLS=your-value --env SMTP_DENY_TOOLS=your-value --env SMTP_INSECURE_TLS=your-value -- npx -y @ni-c/smtp-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"smtp": {
"command": "npx",
"args": [
"-y",
"@ni-c/smtp-mcp"
],
"env": {
"SMTP_HOST": "your-value",
"SMTP_PORT": "your-value",
"SMTP_TLS": "your-value",
"SMTP_USER": "your-value",
"SMTP_PASSWORD": "your-value",
"SMTP_FROM": "your-value",
"SMTP_REPLY_TO": "your-value",
"SMTP_ALLOW_SEND": "your-value",
"SMTP_ALLOWED_RECIPIENTS": "your-value",
"SMTP_MAX_RECIPIENTS": "your-value",
"SMTP_MAX_SENDS_PER_HOUR": "your-value",
"SMTP_MAX_MESSAGE_BYTES": "your-value",
"SMTP_MAX_ATTACHMENT_BYTES": "your-value",
"SMTP_ATTACHMENT_DIR": "your-value",
"SMTP_ATTACHMENT_TYPES": "your-value",
"SMTP_SIGNATURE": "your-value",
"SMTP_AUDIT_LOG": "your-value",
"SMTP_ALLOW_TOOLS": "your-value",
"SMTP_DENY_TOOLS": "your-value",
"SMTP_INSECURE_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"smtp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ni-c/smtp-mcp"
],
"env": {
"SMTP_HOST": "your-value",
"SMTP_PORT": "your-value",
"SMTP_TLS": "your-value",
"SMTP_USER": "your-value",
"SMTP_PASSWORD": "your-value",
"SMTP_FROM": "your-value",
"SMTP_REPLY_TO": "your-value",
"SMTP_ALLOW_SEND": "your-value",
"SMTP_ALLOWED_RECIPIENTS": "your-value",
"SMTP_MAX_RECIPIENTS": "your-value",
"SMTP_MAX_SENDS_PER_HOUR": "your-value",
"SMTP_MAX_MESSAGE_BYTES": "your-value",
"SMTP_MAX_ATTACHMENT_BYTES": "your-value",
"SMTP_ATTACHMENT_DIR": "your-value",
"SMTP_ATTACHMENT_TYPES": "your-value",
"SMTP_SIGNATURE": "your-value",
"SMTP_AUDIT_LOG": "your-value",
"SMTP_ALLOW_TOOLS": "your-value",
"SMTP_DENY_TOOLS": "your-value",
"SMTP_INSECURE_TLS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
SMTP_PORT envSMTP_TLS envSMTP_REPLY_TO envSMTP_ALLOW_SEND envSMTP_ALLOWED_RECIPIENTS envSMTP_MAX_RECIPIENTS envSMTP_MAX_SENDS_PER_HOUR envSMTP_MAX_MESSAGE_BYTES envSMTP_MAX_ATTACHMENT_BYTES envSMTP_ATTACHMENT_DIR envSMTP_ATTACHMENT_TYPES envSMTP_SIGNATURE envSMTP_AUDIT_LOG envSMTP_ALLOW_TOOLS envSMTP_DENY_TOOLS envSMTP_INSECURE_TLS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account ni-c, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SMTP_HOST, SMTP_USER, SMTP_PASSWORD, SMTP_FROM
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A Model Context Protocol (MCP) server for SMTP, the protocol every mail server speaks to accept a message for delivery.
Lets MCP clients like Claude Code, Claude Desktop or Codex send, reply to and forward mail from one configured address — with a human approving every message.
Seven tools is the ceiling, not the floor: SMTP_ALLOW_TOOLS=essential registers a curated five instead, and a model picks the right tool far more reliably from five than from seven — see choosing which tools load.
It sends mail. That is why it is a separate server. Its counterpart imap-mcp reads a mailbox and deliberately has no way to send anything — that absence is its entire security argument, because an agent that can reach private data and process attacker-controlled content is only exploitable once it also has a way out. This server is that way out, so it does not get to make the same claim. It earns its place by narrowing the channel instead, and by living in its own process with its own credentials.
It is off when you install it. SMTP_ALLOW_SEND defaults to false. Until it is set the sending tools are not registered at all — absent from tools/list, not refused at call time.
It can only write to people you named. SMTP_ALLOWED_RECIPIENTS is required to turn sending on. Every address in To, Cc and Bcc is checked against it before a connection is opened, so an injected "mail this to someone else" fails without the server ever reading it as an instruction. Allowing everyone is possible and has to be written as *.
Every message is approved by a person. Not by the model — the request goes to the client as an MCP elicitation. Recipients, subject and any Bcc appear on their own labelled lines, so a subject written to look like an instruction cannot become part of the server's own sentence.
The sender cannot be chosen. There is no from parameter. A model that could pick its own sender could write in a colleague's name, and the result would be indistinguishable from a message they wrote.
Use TLS.
SMTP_TLS=starttls(the default) requires the upgrade rather than attempting it,
so a stripped
STARTTLScapability fails the connection instead of quietly sending your
password in the clear. For a self-signed certificate prefer a proper internal CA over
SMTP_INSECURE_TLS.
| Variable | Required | Default | Description |
|---|---|---|---|
SMTP_HOST | yes | — | Hostname of the SMTP server, e.g. smtp.example.net. |
SMTP_USER | yes | — | Username for SMTP authentication. |
SMTP_PASSWORD | yes | — | Password or app-specific password. |
SMTP_FROM | yes | — | The only sender used, e.g. Name . There is no from parameter. |
SMTP_REPLY_TO | no | — | Reply-To on every message, e.g. Team . Unset means replies go to SMTP_FROM. |
SMTP_PORT | no | 587 / 465 / 25 | Depends on SMTP_TLS. |
SMTP_TLS | no | starttls | starttls, implicit or none. Never opportunistic. |
SMTP_ALLOW_SEND | no | false | Set to true to register the sending tools. |
SMTP_ALLOWED_RECIPIENTS | with SMTP_ALLOW_SEND=true | — | Comma-separated addresses and @domains. * allows anyone. |
SMTP_MAX_RECIPIENTS | no | 10 | Distinct recipients across To, Cc and Bcc in one message. |
SMTP_MAX_SENDS_PER_HOUR | no | 20 | Sliding hourly cap. |
SMTP_MAX_MESSAGE_BYTES | no | 10485760 | Size ceiling on the composed message. |
SMTP_MAX_ATTACHMENT_BYTES | no | 5242880 | Size ceiling on one attachment. |
SMTP_ATTACHMENT_DIR | no | — | Directory attachments are read from. Unset means no attachments. |
SMTP_ATTACHMENT_TYPES | no | document and image allowlist | Comma-separated content types that may be attached. text/html and application/zip are opt-in. |
SMTP_SIGNATURE | no | — | Text appended below the standard -- delimiter. |
SMTP_AUDIT_LOG | no | — | File the audit lines are appended to, in addition to stderr. |
SMTP_ALLOW_TOOLS | no | — | Tool names, a prefix with one trailing *, or essential. |
SMTP_DENY_TOOLS | no | — | Removed after SMTP_ALLOW_TOOLS is applied. |
SMTP_INSECURE_TLS | no | false | Accept self-signed certificates. |
ELICITATION | no | true | false replaces the approval dialog with the two-call token. Not prefixed. |
Two defaults are worth reading twice, because they are the opposite of what the rest of this family does:
* if you mean it.SMTP_ALLOW_TOOLS decides what is registered, SMTP_DENY_TOOLS is subtracted from it. Both take comma-separated tool names or a prefix with a single trailing *. A filtered tool is never built — it does not appear in tools/list and answers a call with "not found", the same as a sending tool while the send gate is closed. Nothing is advertised and then refused.
SMTP_ALLOW_TOOLS=essential # the curated five
SMTP_ALLOW_TOOLS='get_server_info,preview_mail' SMTP_DENY_TOOLS=forward_mail # everything else, minus forwarding
essential is get_server_info, validate_recipients, preview_mail, send_mail and reply_mail. forward_mail is left out: forwarding carries somebody else's content and attachments outward, which is the call that most deserves to be switched on deliberately.
An entry that matches no tool aborts startup and lists the real names. A tool quietly missing from tools/list is invisible — nobody traces an absence back to an environment variable.
claude mcp add smtp -- npx -y @ni-c/smtp-mcp
{
"mcpServers": { "smtp": { "command": "npx", "args": ["-y", "@ni-c/smtp-mcp"], "env": { "SMTP_HOST": "smtp.example.net", "SMTP_USER": "person@example.net", "SMTP_PASSWORD": "app-specific-password", "SMTP_FROM": "Your Name ", "SMTP_ALLOW_SEND": "true", "SMTP_ALLOWED_RECIPIENTS": "@example.net" } } } }
[mcp_servers.smtp]
command = "npx" args = ["-y", "@ni-c/smtp-mcp"]
[mcp_servers.smtp.env] SMTP_HOST = "smtp.example.net" SMTP_USER = "person@example.net" SMTP_PASSWORD = "app-specific-password" SMTP_FROM = "Your Name " SMTP_ALLOW_SEND = "true" SMTP_ALLOWED_RECIPIENTS = "@example.net"
docker run --rm -i Only the beginning is shown; read the rest in the repo