
Apple Mail Actions
io.github.redpop由 GitHub 账号 redpop 发布v0.4.0更新于 Nov 15, 2026
Move messages between mailboxes in Apple Mail on macOS. Needs the Apple Mail read server.
发布方自己的服务:actions.world
概览
仅限 macOS 的配套服务器,让助手在 Apple Mail 中把邮件移动到其他邮箱,并可选地把单个附件保存到本地文件夹。
- 可以做什么
- 在同一账户的邮箱之间移动邮件,每次调用逐条处理并返回每封邮件的状态
- 在开启保存功能时,把某封邮件的一个附件存入交接文件夹并返回文件路径
- 跳过疑似安全邮件、五分钟内已移动过或无法用 Message-ID 识别的邮件
- 提供 doctor 命令,检查辅助应用、自动化权限、Mail 运行状态和受支持的账户
- 适用场景
- 适合让助手整理邮箱:先用配套的只读服务器读取邮件、建议目标文件夹,再真正移动已确认的邮件。只有在同时安装该只读服务器、且 Mail 正在运行的 Mac 上才值得添加。
- 运行要求
- 移动邮件需 macOS 26 或更高版本(macOS 15 可启动但所有移动都会被拒绝);Node.js 22.16 以上或 24 以上;同版本的只读服务器并授予完全磁盘访问权限;Mail 正在运行;通过 setup 命令授予自动化权限。必须设置 APPLE_MAIL_ACCOUNTS,APPLE_MAIL_EXCLUDE_MAILBOXES 应与只读服务器一致。
安装
在 SourceWeft 中
- 打开 控制台中的 Apple Mail Actions,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
apple-mail-actions-mcp
An MCP server with one tool, move_messages, and one
optional tool, save_attachment. It moves messages to another mailbox of the same account in
Apple Mail and, when you switch it on, saves one attachment of a message to a folder. It is the companion of
@redpop/apple-mail-mcp, the read-only server. That package stays read-only;
all moving code lives here.
Background and design decisions for both servers: the article on martin-alker.de.
macOS only. First released as 0.3.2 on 2026-11-12, on npm, as a GitHub release with the
.mcpb, and in the MCP Registry. The plugin follows npm seven days after a release, so it
starts with 0.3.2 once its pin reaches that version (about 2026-11-19).
What it does
Claude looks at your mailbox with the read server, proposes a folder for some messages, and
you confirm. Then Claude calls move_messages with message ids and target mailbox ids. The
package moves messages and, when enabled, saves attachments. It does not send, draft, delete,
flag, create folders, read mail or move between accounts.
The server asks Claude to show the proposal first, with the choices move all, move some, adjust first or move none. That is a request in the server instructions, not a lock. The lock is that the tool is not marked read-only, so your client asks before each call, but only in a mode that asks.
Do not choose "Always allow" for this tool. It turns that confirmation off, and a malicious mail could then make the model move messages without you seeing it.
Use a mode that asks. In Claude Desktop and Cowork, the Auto mode does not ask: an automated check blocks only actions it flags as risky, otherwise Claude moves without asking, even though the tool is set to "Needs approval". Choose Manual for conversations that may move mail. In a test on 2026-11-11, Auto moved a message right after a "yes" in the chat, with no prompt; Manual asked. In Claude Code, modes that approve tools on their own, such as auto mode or skipping permissions, have the same effect.
Saving attachments
save_attachment is off unless APPLE_MAIL_SAVE_ATTACHMENTS is true. While it is off, the
tool does not exist for the model.
Claude calls save_attachment with a message id and the position of the attachment in
attachmentNames of get_message. Mail saves that one attachment into a handover folder, and the tool
returns the file path. The default folder is ~/Library/Caches/apple-mail-mcp/attachments.
Every call gets its own subfolder with a random name like att-k3x9fa, mode 0700. Claude then
moves the file where you want it and reads it with its own tools. Nothing is overwritten, and
nothing is deleted automatically: clean the folder yourself now and then.
Like moving, saving needs the Message-ID header, so it does not work on macOS 15, where
Mail does not store it: every call returns skipped_no_message_id.
If the attachment was not downloaded yet, Mail downloads the attachment from the server first. It then stays in Mail's local storage, as if you had opened the message.
Set APPLE_MAIL_ATTACHMENT_DIR to use another folder, as an absolute path or starting with
~/. macOS protects some folders: ~/Downloads needs its own permission for the program that
runs the server, Claude Desktop or your terminal, and macOS asks for it on the first save. The
folder is checked only when saving is on.
Limits, all set in the environment:
- A file larger than
APPLE_MAIL_MAX_ATTACHMENT_BYTESis refused (default 25 MB, at most 100 MB). - Only file types in
APPLE_MAIL_ATTACHMENT_TYPESare saved. Executable types such asapp,dmg,sh,jsorpyare never allowed; naming one in the variable is a configuration error. - Security mails are never saved, whatever
APPLE_MAIL_SHOW_SECURITY_MAILSsays. - The account must be in
APPLE_MAIL_ACCOUNTSand have a name that Mail can address unambiguously. Gmail and Exchange accounts are allowed for saving but untested; only mailbox.org (IMAP) has been tried.
Saved files are untrusted content from a third party. Do not open them because a mail asks you to.
What you need beside it
This package needs the read server beside it. The read server lists mailboxes and finds
messages; this server only takes the ids it returns. Install @redpop/apple-mail-mcp first
and give it Full Disk Access as its README describes.
Two settings must match across both servers, because neither server sees the other's configuration:
APPLE_MAIL_ACCOUNTSis required here. If it is empty, every call fails withCONFIG_INVALID; moving is never enabled for all accounts. Use the same list in the read server.- Set
APPLE_MAIL_EXCLUDE_MAILBOXESin both servers. A mailbox hidden in the read server but not here would still be a possible target.
Junk and trash are not visible by default, in either server.
What it moves, and what it refuses
Targets are all visible mailboxes except trash, junk, drafts, sent and "all mail". Sources
must be visible under the same rules, so junk and trash are not sources by default. Further
targets can be forbidden with APPLE_MAIL_MOVE_EXCLUDE_TARGETS.
Each message gets one status. moved means the index of Mail shows it in the target and no
longer in the source. moved_unverified means the move was requested but the index did not
confirm it within 10 seconds. Both describe the local state in Mail, not the mail server.
failed and the skipped_* statuses say why a message did not move; nothing was changed for
those.
Message ids are valid for the current index only. After Mail rebuilds a mailbox, or after a
skipped_not_found status, search again and use the new ids.
Messages are skipped, never moved, in these cases:
- The message looks like a security mail (verification code, password reset, sign-in link).
The check looks at the subject only; the message text is not read.
APPLE_MAIL_SHOW_SECURITY_MAILSdoes not lift it. - The message was moved in the last 5 minutes. Rapid back and forth can create a copy on the mail server, so each moved message is locked for 5 minutes, across processes. Moves you make yourself in Mail are not known to the lock.
- The message is visible in several mailboxes and
sourceMailboxIddoes not pick one. - The message has no Message-ID header in Mail's index. On macOS 15 Mail does not store it, so
the tool cannot move anything there.
doctorsays so. - The source and target are the same, or in different accounts.
- The account is not supported. Only mailbox.org has been tested. Other IMAP providers are
untested: they run without a refusal, so limit
APPLE_MAIL_ACCOUNTSto accounts you are willing to try. Gmail, Exchange and local folders are refused for moving. - A folder name differs from another folder of the account only in case, or contains control characters.
Moves run one after another, never in parallel, and are never retried: a failed move may have arrived halfway.
A folder that never held a message is not in Mail's index, so it does not appear in
list_mailboxes and cannot be a target. Put one message in it by hand first.
Subfolders and INBOX have had one manual test: on 2026-11-04, on macOS 27 with one IMAP account at mailbox.org, one test mail was moved to a subfolder and back, and one test mail to INBOX and back, 60 seconds apart, with no copy in the webmail. These were single test mails, not a series.
Requirements
- macOS 26 or later to move mail. The server starts on macOS 15, but Mail there does not store
the Message-ID header, so every move is refused with
skipped_no_message_id; the server never moves a message it cannot identify by its Message-ID. Verified with a real mailbox only on macOS 27 with Mail 16 and one mailbox.org account. - Node.js 22.16 or newer in the 22 line, or 24 and newer.
- The read server
@redpop/apple-mail-mcpat the same version, with Full Disk Access. - Mail must be running. The server never starts it; without it the call fails with
MAIL_NOT_RUNNING.
Install
Claude Code, as a plugin:
Claude Code without the plugin:
Claude Desktop and Cowork: download apple-mail-actions-mcp-<version>.mcpb from the
latest release and open it. It
carries both apps and needs no npm. It has the same settings page. Claude Desktop does not switch it on after the install, because the accounts setting is
required; enter the accounts, save, and switch it on under Settings > Extensions. The plugin does not work in Cowork, which starts a plugin's local server inside its Linux
virtual machine, away from Mail, or in the desktop chat, which ignores such servers.
setup first runs the setup of the read server (Full Disk Access for its helper), then asks
macOS for the Automation permission of "Mail MCP Actions" to control Mail. Mail must be
running for the dialog to appear. The permission goes to that small app alone, not to Claude,
your terminal or Node. It can be switched off under System Settings > Privacy & Security >
Automation.
Configuration
Set these in the environment of the server. They cannot be changed through tool parameters.
An invalid value does not stop the server; every call then fails with CONFIG_INVALID naming
the setting. The server reads them once, at startup: restart the client after a change.
The settings of the read server that do not appear here, for example body search, do not affect this package.
Install from source
You need the Xcode Command Line Tools and an Apple Development certificate for a build that keeps its permission across rebuilds.
Then follow the README of the read server for its helper, and grant Automation with
node packages/actions/dist/index.js setup, with APPLE_MAIL_ACTIONS_PATH and
APPLE_MAIL_HELPER_PATH pointing at the Dev bundles in each bin/ directory. Never sign
these builds with a Developer ID.
Put these variables in front of the command instead of exporting them. An exported
APPLE_MAIL_* variable stays in the shell, and every MCP server that a client started from
that shell inherits it: an exported APPLE_MAIL_ACCOUNTS also limits the read server to those
accounts. If you exported them, run unset on them before you start the client.
Diagnostics
doctor runs the checks of the read server, then checks the Actions app and its signature,
the Automation permission, whether Mail is running, whether the Message-ID column exists and
which accounts are supported. Without --verbose it names no accounts or addresses. Exit code
1 means at least one check failed.
Privacy Policy
This policy covers the server and the Actions app, as published on npm and in the GitHub releases. It adds to the policy of the read server.
What is collected
Nothing is collected by the author or by any service. The server has no telemetry, and neither
the server nor the app opens a network connection. The app never sees mail content. It receives
a message number, a Message-ID and the names of an account and two mailboxes, and returns a
status. For save_attachment it also receives the part id and file name of one attachment and a slot name for the handover subfolder.
How it is used and stored
When your AI client calls move_messages, the app asks Mail to move the messages you named. The
server writes one file, move-locks.json, under
~/Library/Application Support/apple-mail-mcp/, directory 0700, file 0600. It holds the
internal message numbers of recently moved messages and the time their lock ends. No names or
subjects.
With APPLE_MAIL_SAVE_ATTACHMENTS on, save_attachment has Mail write one attachment into the
handover folder, which stays on your Mac until you delete it. The server and the app do not read
the file.
Sharing with third parties
Nothing is shared. Mail itself synchronizes the move with your mail server, as it does for a move you make by hand. The statuses of a call go back to your AI client.
Retention
Entries leave the lock file after 5 minutes at the next move. Delete the file at any time. The
server never deletes or changes anything under ~/Library/Mail itself; the moves are Mail's.
Contact
Questions about this policy: open an issue at
https://github.com/redpop/apple-mail-mcp/issues. Security problems: report them privately as
SECURITY.md describes.
License
MIT, see LICENSE.
来源:packages/actions/README.md,提交 daf547d
工具
0版本历史
2- v0.4.0最新Nov 14, 2026
- v0.3.2Nov 12, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Actions 集成
actions.world
world.actions官方发布者
远程 MCP 服务器,让助手在 actions.world 数据集上运行视频操作并跟踪运行结果。

Meeting decisions and actions extract — Atom
org.aimlds
Meeting decisions and actions extract — Atom 的托管 MCP 服务,由 aimlds.org 发布;需要凭据;Streamable HTTP。

MCP Safe Actions
由 GitHub 账号 techsaurabh-394 发布
File server whose delete tool asks a human first (elicitation or one-time token), with audit log.

NSE Corporate Announcements (Apify) - NSE India filings, corporate actions, bulk and block deals
由 GitHub 账号 datadmon 发布
托管在 Apify 上的 MCP 服务器,以 JSON 返回印度 NSE 公司披露信息:公告、除权日、董事会会议、大宗与批量交易及评级。

BSE Corporate Announcements (Apify) - BSE India filings, corporate actions, bulk and block deals
由 GitHub 账号 datadmon 发布
由 Apify 托管的 MCP 端点,以 JSON 返回印度 BSE 公司披露信息:公告、除权日、董事会会议、业绩日期和大宗交易。