Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
MCP server that sends mail over SMTP, gated behind an allowlist and a human confirmation
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
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「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、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"
}
}
}
}ターミナルでこれを実行します
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動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
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 envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント ni-c で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:SMTP_HOST, SMTP_USER, SMTP_PASSWORD, SMTP_FROM
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.2.0)がレジストリに届いたのは2 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.js, Dockerも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Signoff
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
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.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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 冒頭だけを表示しています。続きはリポジトリで読めます