Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
MCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
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_TLSLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu 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-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
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 envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub ni-c, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: SMTP_HOST, SMTP_USER, SMTP_PASSWORD, SMTP_FROM
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.2.0) llegó al registro hace 2 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js, Docker en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Excaliself
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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 Solo se muestra el principio; lee el resto en el repo