Mailu 邮箱 MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Mailu 邮箱 MCP
自用项目 · 本仓库主要供维护者自用。
使用所配置 Mailu 站点的原生 REST API 管理邮箱和别名,可通过单独授权的 IMAP 账号读取邮件。
安装和认证
Python 3.11+。运行 python -m venv .venv 后,在该环境中运行 python -m pip install -r requirements.txt。设置 MAILU_API_URL 为实际原生 API 地址(含 /api/v1),MAILU_API_TOKEN_FILE 为自己的令牌文件。读取邮件还需配置 MAILU_IMAP_HOST、MAILU_IMAP_USER、MAILU_IMAP_PASSWORD_FILE;默认使用 TLS 的 993 端口。支持邮箱与别名查询、创建、消息头和正文读取。创建邮箱时,在仅管理员可读的 MAILU_NEW_PASSWORD_DIR 内预置以小写邮箱地址的 SHA-256 加 .txt 命名的初始密码文件。别名目标限已存在的本地邮箱。Mailu REST API
使用 python client_config.py cursor、python client_config.py dsh 或 python client_config.py codex 输出对应客户端的配置。将其合并到已有 MCP 或 DSH 插件列表。配置生成器接受重复的 --env NAME=VALUE 以传递路径和站点设置。
Related MCP server: Email MCP Server
多账号和终端更新
MCP 入口为 router.py,需要 Python 3.11+。主机在本地保存账号配置,默认位置为 ~/.config/ldai-mcp/mailu/accounts.json,也可用 LDAI_ACCOUNTS_FILE 指定。复制 两账号示例,将地址与路径换成自己的值。每个账号可以对应不同的 Mailu 站点、管理令牌或 IMAP 邮箱。只读个人收件箱时仅需该账号的 IMAP 配置。
ldai_accounts 仅列出别名和连接状态。配置两个账号后,工具以 work__ 和 personal__ 前缀区分,所选工具始终进入该账号的独立子进程。已有单账号配置继续使用原工具名。运行 python profile_exec.py work -- <程序> <参数…> 可在同一账号环境完成登录或初始化。完成配置后重新连接 MCP。需要自有适配器时,管理员可为某个账号填写可信 stdio 程序的 command、args 和 env;连接器仅发布当前产品前缀下的业务工具。
安装本仓库后,其他终端可运行 git pull --ff-only;Python 服务在其虚拟环境执行 python -m pip install -r requirements.txt,随后重新加载客户端。需要固定版本时可检出发布标签。
维护者在 main 提交改进、运行测试,并同步更新 connector.json、两个插件清单的版本,再执行 python build_plugin.py --push。此命令将 main 与版本标签一起推送到本仓库,再从已提交文件生成 ZIP。更新既有账号插件时传 --account-name <既有包名>,把生成的 ZIP 发布到同一插件。包内 release-source.json 记录精确提交,可与各终端核对。Git 推送与账号插件发布是两个独立步骤。
许可为 AGPL-3.0-only。许可全文
实现参考
按 Mailu 原生资源实现邮箱和别名操作,并对照社区连接器的认证与资源映射。GitHub 统计核对日期为 2026-11-11。
Mailu/Mailu · 7614 stars,默认分支 5425 次提交
manganate006/mailu-mcp · 0 stars,默认分支 19 次提交
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read the verification code (OTP) and test emails your app sends to a catch-all test hostname. Four read-only tools: list_domains, get_latest_otp, list_messages, get_message. Needs a MailBots API key from the 14-day free trial (no card, no DNS) or a paid plan. Setup: https://mailbots.top/docs/mcp
Hosted email MCP for your own Gmail, Outlook.com, Microsoft 365, iCloud or IMAP inbox: read, search, draft, reply in thread, forward and file mail. It moves or flags up to 500 messages in one call, and a send leaves exactly one copy in Sent. A calendar is a separate connection, and connecting one adds diary and scheduling tools.
Your agent needs a mailbox of its own — to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** • "Create an inbox for this agent and tell me its address." • "Read the new messages in this thread and draft a reply." • "Send this message with the attachment and wait for the response." • "Search this inbox for everything from that domain." • "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries — reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.
Email, calendar and contacts for AI agents: Gmail, Microsoft 365 and IMAP accounts behind one API.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables email management for a single mailbox via IMAP and SMTP protocols. Supports reading, searching, and sending emails with threading support through stdio or HTTP transports.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, reply, forward, schedule, and analyze email across multiple IMAP/SMTP accounts, with drafts and templates, provider-aware labels and bulk operations, calendar extraction, real-time inbox watching with AI triage, and verification-code capture. Exposes 52 tools, 7 prompts, and 6 resources over stdio or Streamable HTTP, with OAuth2 support for Gmail and Microsoft 365.28 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, schedule, manage, and analyze mail across multiple IMAP/SMTP accounts, with provider-aware labels, real-time IDLE watching, verification-code capture, and OAuth2 support. Connects over stdio or Streamable HTTP, exposing 52 tools, 7 prompts, and 6 resources with a guided setup wizard.28 npmISC
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to read, search, send, schedule, manage, and analyze mail across multiple IMAP/SMTP accounts, including drafts, provider-aware labels, real-time IDLE triage, verification-code capture, and calendar extraction. Runs over stdio for local clients or Streamable HTTP for networked access, with a guided setup wizard and OAuth2 support.-