Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

SMTP

by ni-cversion 0.2.0i★ –iRuns on your computer
Registry nameio.github.ni-c/smtp-mcp

Install

Overview

Description from the maker (original English)

MCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: SMTP_HOST, SMTP_USER, SMTP_PASSWORD, SMTP_FROM

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: 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_TLS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • SMTP_HOST required env
    Hostname of the SMTP server, e.g. smtp.example.net.
  • SMTP_PORT env
    Port. Defaults to 587 for starttls, 465 for implicit, 25 for none.
  • SMTP_TLS env
    starttls (default), implicit or none. STARTTLS is required, never opportunistic.
  • SMTP_USER required env
    Username for SMTP authentication.
  • SMTP_PASSWORD secret required env
    Password or app-specific password for SMTP authentication.
  • SMTP_FROM required env
    The only sender this server will use, e.g. "Name ". There is no from parameter.
  • SMTP_REPLY_TO env
    Reply-To header on every message, e.g. "Team ". Unset means no Reply-To header and replies go to SMTP_FROM. There is no reply_to parameter.
  • SMTP_ALLOW_SEND env
    Set to "true" to register the sending tools. Defaults to false: the server cannot send until it is set.
  • SMTP_ALLOWED_RECIPIENTS env
    Comma-separated addresses and @domains this server may write to. Required with SMTP_ALLOW_SEND=true; "*" allows any.
  • SMTP_MAX_RECIPIENTS env
    Maximum distinct recipients across To, Cc and Bcc in one message. Default 10.
  • SMTP_MAX_SENDS_PER_HOUR env
    Sliding hourly cap on messages sent. Default 20.
  • SMTP_MAX_MESSAGE_BYTES env
    Maximum size of the composed message. Default 10485760.
  • SMTP_MAX_ATTACHMENT_BYTES env
    Maximum size of a single attachment. Default 5242880.
  • SMTP_ATTACHMENT_DIR env
    Directory attachments are read from. Unset means attachments are unavailable.
  • SMTP_ATTACHMENT_TYPES env
    Comma-separated content types that may be attached. Defaults to a document and image allowlist.
  • SMTP_SIGNATURE env
    Text appended below the standard signature delimiter of every message.
  • SMTP_AUDIT_LOG env
    File the audit lines are appended to, in addition to stderr.
  • SMTP_ALLOW_TOOLS env
    Comma-separated tool names, a prefix with one trailing *, or "essential" for the curated preset.
  • SMTP_DENY_TOOLS env
    Comma-separated tool names or prefixes to remove, applied after SMTP_ALLOW_TOOLS.
  • SMTP_INSECURE_TLS env
    Set to "true" to accept self-signed certificates. Prefer a proper internal CA.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ni-c, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18398 servers in this category
  • Published to the registry more recently than 33% of the other 18398 servers in this category
  • Basic checks equal to or better than 100% of the other 18398 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SMTP safe?

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.

What keys or codes does it need?

You need to fill in: SMTP_HOST, SMTP_USER, SMTP_PASSWORD, SMTP_FROM

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 3 days ago
Install

Tethered Trust

by tetheredtrust.com

Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

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.

smtp-mcp

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.

What makes it different

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.

Requirements

  • Node.js 24 or newer
  • An SMTP account you may send from — a submission server on port 587 or 465, with a username and password. Providers with two-factor authentication generally need an app-specific password.

Configuration

Use TLS. SMTP_TLS=starttls (the default) requires the upgrade rather than attempting it,

so a stripped STARTTLS capability 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.

VariableRequiredDefaultDescription
SMTP_HOSTyes—Hostname of the SMTP server, e.g. smtp.example.net.
SMTP_USERyes—Username for SMTP authentication.
SMTP_PASSWORDyes—Password or app-specific password.
SMTP_FROMyes—The only sender used, e.g. Name . There is no from parameter.
SMTP_REPLY_TOno—Reply-To on every message, e.g. Team . Unset means replies go to SMTP_FROM.
SMTP_PORTno587 / 465 / 25Depends on SMTP_TLS.
SMTP_TLSnostarttlsstarttls, implicit or none. Never opportunistic.
SMTP_ALLOW_SENDnofalseSet to true to register the sending tools.
SMTP_ALLOWED_RECIPIENTSwith SMTP_ALLOW_SEND=true—Comma-separated addresses and @domains. * allows anyone.
SMTP_MAX_RECIPIENTSno10Distinct recipients across To, Cc and Bcc in one message.
SMTP_MAX_SENDS_PER_HOURno20Sliding hourly cap.
SMTP_MAX_MESSAGE_BYTESno10485760Size ceiling on the composed message.
SMTP_MAX_ATTACHMENT_BYTESno5242880Size ceiling on one attachment.
SMTP_ATTACHMENT_DIRno—Directory attachments are read from. Unset means no attachments.
SMTP_ATTACHMENT_TYPESnodocument and image allowlistComma-separated content types that may be attached. text/html and application/zip are opt-in.
SMTP_SIGNATUREno—Text appended below the standard -- delimiter.
SMTP_AUDIT_LOGno—File the audit lines are appended to, in addition to stderr.
SMTP_ALLOW_TOOLSno—Tool names, a prefix with one trailing *, or essential.
SMTP_DENY_TOOLSno—Removed after SMTP_ALLOW_TOOLS is applied.
SMTP_INSECURE_TLSnofalseAccept self-signed certificates.
ELICITATIONnotruefalse 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:

  • `SMTP_ALLOW_SEND` is off. A freshly installed smtp-mcp can compose and preview messages and cannot send any.
  • An unset `SMTP_ALLOWED_RECIPIENTS` is a startup error, not "anyone". Treating a missing line as permission is how an accident becomes a delivered message. Write * if you mean it.
Choosing which tools load

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.

Installation

Claude Code
claude mcp add smtp -- npx -y @ni-c/smtp-mcp
Claude Desktop
{

"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" } } } }

Codex
[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
docker run --rm -i 

Only the beginning is shown; read the rest in the repo

Ask PopNx