WeCom Mail MCP
Related Servers
Alternatives to WeCom Mail MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityDmaintenance通过IMAP和SMTP协议实现邮箱读写操作,支持腾讯企业邮箱,可收发邮件、管理文件夹和搜索邮件。532 npm1MIT- AlicenseBqualityCmaintenanceEnables sending, listing, and reading email messages via IMAP/POP3 with support for multiple providers, including NetEase, QQ, Gmail, and Outlook.7MIT
- AlicenseNot gradedqualityCmaintenanceA mail service that connects private domain email to MCP clients, enabling sending (with auto signature), receiving, and reading emails through natural language via stdio or SSE transport.MIT
- FlicenseNot gradedqualityBmaintenanceEnables 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.-
- FlicenseAqualityDmaintenanceEnables sending emails through SMTP with support for multiple recipients, attachments, CC/BCC, and both plain text and HTML formats. Includes preset configurations for common email providers like Gmail, QQ, Outlook, and 163.5-
- AlicenseBqualityBmaintenanceEnables AI agents to securely interact with Gmail and QQ Mail, including IMAP search/read/organization, attachments, and preview-confirmed sending.411MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one sends email, the other retrieves mailbox information. There is no overlap or ambiguity that could lead to misselection.
Both names use a verb_noun pattern (send_email, get_mailbox_info), which is consistent and predictable. Minor deviation in specificity but acceptable.
With only 2 tools, the set feels thin for an email MCP server. Common operations like listing, reading, or managing emails are absent, making the count borderline inadequate.
The server only supports sending email and checking mailbox info. Critical lifecycle operations such as reading, replying, forwarding, or managing folders are missing, significantly limiting its usefulness for email workflows.