原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Email (IMAP/SMTP)

作者:mindstone版本 0.3.2i★ –i在你的电脑上运行
注册名称io.github.mindstone/mcp-server-email-imap

安装

概览

作者提供的说明(英文原文)

Email IMAP/SMTP MCP server: iCloud, Gmail, Yahoo, Outlook, and custom IMAP providers

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 聊天与邮件
  • 你需要填写:EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD, EMAIL_IMAP_PROVIDER, EMAIL_IMAP_IMAP_HOST, EMAIL_IMAP_SMTP_HOST, EMAIL_IMAP_IMAP_PORT, EMAIL_IMAP_SMTP_PORT, EMAIL_IMAP_MAX_RECIPIENTS, EMAIL_IMAP_RATE_LIMIT_PER_HOUR, EMAIL_IMAP_RATE_LIMIT_WINDOW_MS, MCP_WORKSPACE_PATH

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "email-imap": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-email-imap"
      ],
      "env": {
        "EMAIL_IMAP_EMAIL": "your-value",
        "EMAIL_IMAP_PASSWORD": "your-value",
        "EMAIL_IMAP_PROVIDER": "your-value",
        "EMAIL_IMAP_IMAP_HOST": "your-value",
        "EMAIL_IMAP_SMTP_HOST": "your-value",
        "EMAIL_IMAP_IMAP_PORT": "your-value",
        "EMAIL_IMAP_SMTP_PORT": "your-value",
        "EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
        "MCP_WORKSPACE_PATH": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add email-imap --env EMAIL_IMAP_EMAIL=your-value --env EMAIL_IMAP_PASSWORD=your-value --env EMAIL_IMAP_PROVIDER=your-value --env EMAIL_IMAP_IMAP_HOST=your-value --env EMAIL_IMAP_SMTP_HOST=your-value --env EMAIL_IMAP_IMAP_PORT=your-value --env EMAIL_IMAP_SMTP_PORT=your-value --env EMAIL_IMAP_MAX_RECIPIENTS=your-value --env EMAIL_IMAP_RATE_LIMIT_PER_HOUR=your-value --env EMAIL_IMAP_RATE_LIMIT_WINDOW_MS=your-value --env MCP_WORKSPACE_PATH=your-value -- npx -y @mindstone/mcp-server-email-imap

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "email-imap": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-email-imap"
      ],
      "env": {
        "EMAIL_IMAP_EMAIL": "your-value",
        "EMAIL_IMAP_PASSWORD": "your-value",
        "EMAIL_IMAP_PROVIDER": "your-value",
        "EMAIL_IMAP_IMAP_HOST": "your-value",
        "EMAIL_IMAP_SMTP_HOST": "your-value",
        "EMAIL_IMAP_IMAP_PORT": "your-value",
        "EMAIL_IMAP_SMTP_PORT": "your-value",
        "EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
        "MCP_WORKSPACE_PATH": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "email-imap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-email-imap"
      ],
      "env": {
        "EMAIL_IMAP_EMAIL": "your-value",
        "EMAIL_IMAP_PASSWORD": "your-value",
        "EMAIL_IMAP_PROVIDER": "your-value",
        "EMAIL_IMAP_IMAP_HOST": "your-value",
        "EMAIL_IMAP_SMTP_HOST": "your-value",
        "EMAIL_IMAP_IMAP_PORT": "your-value",
        "EMAIL_IMAP_SMTP_PORT": "your-value",
        "EMAIL_IMAP_MAX_RECIPIENTS": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "your-value",
        "EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "your-value",
        "MCP_WORKSPACE_PATH": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • EMAIL_IMAP_EMAIL 必填 env
    Email address
  • EMAIL_IMAP_PASSWORD 机密 必填 env
    App-specific password
  • EMAIL_IMAP_PROVIDER env
    Provider — icloud, gmail, yahoo, outlook, or custom (auto-detected from email domain if unset)
  • EMAIL_IMAP_IMAP_HOST env
    Custom IMAP host (for provider=custom)
  • EMAIL_IMAP_SMTP_HOST env
    Custom SMTP host (for provider=custom)
  • EMAIL_IMAP_IMAP_PORT env
    Custom IMAP port
  • EMAIL_IMAP_SMTP_PORT env
    Custom SMTP port
  • EMAIL_IMAP_MAX_RECIPIENTS env
    Safety cap: maximum combined To+CC+BCC recipients per email_send call. Defaults to 25; raising bypasses spam-prevention guardrails against prompt-injection-driven mass sends.
  • EMAIL_IMAP_RATE_LIMIT_PER_HOUR env
    Safety cap: maximum email_send calls per rolling window. Defaults to 50; protects against runaway sends when injection content escapes the LLM's intent.
  • EMAIL_IMAP_RATE_LIMIT_WINDOW_MS env
    Sliding-window length for the rate limit (ms)
  • MCP_WORKSPACE_PATH env
    Workspace directory that email_get_attachment downloads into (fresh email-imap-attachment-* staging directories). Defaults to the system temp directory.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 mindstone 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 1787 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1787 个服务器的 22% 更新
  • 基础检查结果等于或优于此分类中其他 1787 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Email (IMAP/SMTP) 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.2)于3个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它?

同一分类中有:Vexa, emailmd, MCP WhatsApp Cloud

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Vexa

作者:Vexa-ai

Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.

在云端运行★ 2,949Apache-2.02个月前更新
安装

emailmd

作者:anypost

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

电脑或云端★ 1,385MIT32天前更新
安装

MCP WhatsApp Cloud

作者:codespar

MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API

在你的电脑上运行★ 277MIT5个月前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@mindstone/mcp-server-email-imap

Email IMAP/SMTP MCP server for Model Context Protocol hosts. Read, search, send, and manage emails through IMAP and SMTP — supports iCloud Mail, Gmail, Yahoo Mail, Outlook / Microsoft 365, and custom IMAP providers.

Status

  • Version: 0.3.2 · npm
  • Auth: App password (EMAIL_IMAP_PASSWORD)
  • Tools: 17 (mailbox, messages, drafts, send)
  • Surface: local-protocol
  • Machine-readable: STATUS.json

Requirements

  • Node.js 20+
  • npm

One-click install

After clicking the button, your host will prompt you to fill: EMAIL_IMAP_EMAIL, EMAIL_IMAP_PASSWORD, EMAIL_IMAP_IMAP_PORT, EMAIL_IMAP_SMTP_PORT, EMAIL_IMAP_MAX_RECIPIENTS, EMAIL_IMAP_RATE_LIMIT_PER_HOUR, EMAIL_IMAP_RATE_LIMIT_WINDOW_MS.

Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Email (IMAP/SMTP))

{

"mcpServers": { "Email (IMAP/SMTP)": { "command": "npx", "args": [ "-y", "@mindstone/mcp-server-email-imap" ], "env": { "EMAIL_IMAP_EMAIL": "", "EMAIL_IMAP_PASSWORD": "", "EMAIL_IMAP_IMAP_PORT": "993", "EMAIL_IMAP_SMTP_PORT": "587", "EMAIL_IMAP_MAX_RECIPIENTS": "25", "EMAIL_IMAP_RATE_LIMIT_PER_HOUR": "50", "EMAIL_IMAP_RATE_LIMIT_WINDOW_MS": "3600000" } } } }

Quick Start

Install & build
cd <path-to-repo>/connectors/email-imap

npm install npm run build

npx (once published)
npx -y @mindstone/mcp-server-email-imap
Local
node dist/index.js

Configuration

Environment variables
  • EMAIL_IMAP_EMAIL — email address
  • EMAIL_IMAP_PASSWORD — app-specific password
  • EMAIL_IMAP_PROVIDER — email provider (icloud, gmail, yahoo, outlook, or custom). When unset, the connector auto-detects the provider from the email's domain (e.g. @gmail.com → gmail, @icloud.com → icloud, @outlook.com → outlook, @yahoo.co.uk → yahoo). If the domain is not recognised, the connector refuses to start with a clear error — it will not silently fall back to a default provider.
  • EMAIL_IMAP_IMAP_HOST — custom IMAP host (optional, for custom providers)
  • EMAIL_IMAP_SMTP_HOST — custom SMTP host (optional, for custom providers)
  • EMAIL_IMAP_IMAP_PORT — custom IMAP port (default: 993). Cleartext ports (imap_port=143, smtp_port=25) are allowed when configured — your host owns the plaintext decision.
  • EMAIL_IMAP_SMTP_PORT — custom SMTP port (default: 587)
  • MCP_WORKSPACE_PATH — workspace directory used for attachment file I/O. email_get_attachment downloads into a fresh, private email-imap-attachment-* staging directory created directly under this path (the returned path points there), and outbound attachments on email_send / email_save_draft / email_update_draft may only be read from inside it (paths outside — including via symlinks — are refused). Successful downloads keep their staging directory (it is the container of the returned file); accumulated email-imap-attachment-* directories are safe to delete once the files are no longer needed. Defaults to the system temp directory when unset.
  • MCP_HOST_BRIDGE_STATE — optional path to a host bridge state file used for credential management
  • MINDSTONE_REBEL_BRIDGE_STATE — backwards-compatible alias for MCP_HOST_BRIDGE_STATE
Send-side caps (email_send)

These caps act as blast-radius circuit breakers against prompt-injection-driven mass sends. Defaults are baked into the source so a host that sets none of these still gets safe behaviour. Hosts can tighten them per deployment.

  • EMAIL_IMAP_MAX_RECIPIENTS — maximum combined To+CC+BCC recipients per email_send call (default: 25). Exceeding this returns a structured error with code: "RECIPIENT_LIMIT_EXCEEDED".
  • EMAIL_IMAP_RATE_LIMIT_PER_HOUR — maximum number of email_send calls per rolling window (default: 50). Exceeding this returns a structured error with code: "RATE_LIMIT_EXCEEDED", plus resetAt (ISO-8601) and retryAfterMs so the host/LLM can back off.
  • EMAIL_IMAP_RATE_LIMIT_WINDOW_MS — sliding-window length, in milliseconds, for the rate limit (default: 3600000 — one hour).

Host configuration examples

Claude Desktop / Cursor
{

"mcpServers": { "Email": { "command": "npx", "args": ["-y", "@mindstone/mcp-server-email-imap"], "env": { "EMAIL_IMAP_EMAIL": "you@icloud.com", "EMAIL_IMAP_PASSWORD": "your-app-specific-password", "EMAIL_IMAP_PROVIDER": "icloud" } } } }

Local development (no npm publish needed)
{

"mcpServers": { "Email": { "command": "node", "args": [" /connectors/email-imap/dist/index.js"], "env": { "EMAIL_IMAP_EMAIL": "you@icloud.com", "EMAIL_IMAP_PASSWORD": "your-app-specific-password", "EMAIL_IMAP_PROVIDER": "icloud" } } } }

Security: host confirmation required for email_send

email_send is a destructive, open-world action: it dispatches mail to arbitrary external recipients on the user's behalf. The tool is annotated with destructiveHint: true and openWorldHint: true accordingly.

Hosts MUST require explicit user confirmation before each `email_send` invocation. A user-confirmation gate is the only reliable defence against prompt-injection content (e.g., text inside an email_get_message body) coercing the LLM into sending mail without the user's intent. Do not auto-approve email_send based on tool annotations alone — surface the full recipient list, subject, and body to the user and require an affirmative click/keystroke before forwarding the call to the connector.

The connector additionally enforces:

  • A combined To+CC+BCC recipient cap (EMAIL_IMAP_MAX_RECIPIENTS, default 25).
  • A per-process rolling rate limit (EMAIL_IMAP_RATE_LIMIT_PER_HOUR / EMAIL_IMAP_RATE_LIMIT_WINDOW_MS, defaults 50 / 3600000ms).

When either cap is exceeded the tool returns a structured error JSON ({ ok: false, code: "RECIPIENT_LIMIT_EXCEEDED" | "RATE_LIMIT_EXCEEDED", … }) without contacting the SMTP transport. Caps are env-tunable but defaults are baked into the source — hosts do not need to set any env var to get safe behaviour.

Security: untrusted-content envelopes and destructive tools

Every attacker-controlled text field the connector returns — message bodies, subjects, from/to display names, Message-IDs, attachment filenames, MIME content types and part identifiers, mailbox names and special-use values, message flag keywords (writable via email_set_flags, where keywords must match a conservative charset allowlist — letters, digits, _, $, ., - with an optional leading \ — so atom-specials like spaces, parens, quotes or CR/LF can never reach the IMAP command), draft summaries, and error text originating from the IMAP/SMTP server or vendor SDKs — is wrapped in an … envelope (with close-tag breakout escaping) so the host LLM treats it as data, not instructions. Tools that consume a previously returned value (mailbox, part, mailbox names, flag keywords) accept the enveloped form as-is and strip one envelope layer on input.

Beyond email_send, the tools annotated destructiveHint: true are email_save_draft, email_update_draft (replaces and expunges the old draft), email_create_mailbox, email_rename_mailbox, email_delete (permanent when no Trash mailbox exists; aborts with a TRASH_MOVE_FAILED error — leaving the messages in place — when the move to Trash fails, rather than silently escalating to a permanent expunge), email_move_messages (its fallback permanently expunges the source messages, and only after the copy to the destination is verified complete for every UID — otherwise it aborts with a MOVE_COPY_UNVERIFIED error), email_set_flags (\Deleted marks messages for permanent expunge on mailbox close), email_delete_draft (always permanent), and email_delete_mailbox (removes the folder and all messages inside it). Hosts should gate these behind the same explicit user confirmation as email_send.

Tools (17)

Configuration
  • configure_email_imap — Configure email account credentials and provider
Mailbox
  • email_list_mailboxes — List all email folders/mailboxes with message counts
  • email_get_mailbox_status — Get mailbox status with unread count and latest subjects
  • email_create_mailbox — Create a new mailbox/folder (destructive)
  • email_rename_mailbox — Rename a mailbox/folder (INBOX cannot be renamed; destructive)
  • email_delete_mailbox — Permanently delete a mailbox/folder and its contents (destructive)
Messages
  • email_search_messages — Search emails with sender/subject/unread filters, since/before date filters, and before_uid cursor pagination (returns at most 50 messages when limit is omitted; hasMore: true signals more results)
  • email_get_message — Get full email content by UID (bodies, subjects, addresses, Message-ID, and attachment filenames/MIME metadata are returned inside envelopes)
  • email_get_attachment — Download an attachment into the workspace sandbox (see MCP_WORKSPACE_PATH); writes are exclusive-create, so existing files are never overwritten
  • email_move_messages — Move emails between folders (fallback expunge of the source is gated on a verified

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx