AliMail Admin MCP
Related Servers
Alternatives to AliMail Admin MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search, read, organize, and draft mail in a serverless mailbox system, with optional send permissions, scope-based access control, and audit logging.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants and compatible clients to securely search, read, send, reply, forward, organize, and bulk-delete email across multiple mailboxes, with automatic SMTP configuration and AES-256-encrypted credential storage.931 npmMIT

The-Y CRM MCP serverofficial
FlicenseNot gradedqualityCmaintenanceLets AI programs such as Claude or ChatGPT set up and run a shared inbox for calls, WhatsApp, email and web chat, covering mailboxes, phone extensions and ring groups, contacts, deals, tasks and reply drafts. Every action stays within permissions the account owner chooses and is recorded in the account's log.-- AlicenseBqualityBmaintenanceEnables AI assistants and other MCP clients to manage mailboxes, domains, routing rules, app passwords, and account credit through the Purelymail API, with optional read-only exposure.19405 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage MSP-multi-tenant email security: organizations, domains, users, licensing, features, subscription packages, and email flow reporting.Apache 2.0
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Migadu email hosting services through natural language, including creating mailboxes, setting up aliases, configuring autoresponders, and handling bulk operations efficiently.3531 PyPI17MIT
TDQS
Scored across 11 tools
The get/list department trio (get_department, get_departments_by_ids, get_department_chain) and the tree-vs-subdepartment pair (get_department_tree vs list_sub_departments) have some conceptual overlap, but descriptions explicitly cross-reference each other ("需要整棵树请用 get_department_tree") to route the agent correctly. Single-vs-batch (get_user vs get_users_by_ids) and user-vs-department listing are clearly distinguished.
All 11 tools follow a strict verb_noun snake_case convention: list_*, get_*, with suffixes clearly indicating batch (_by_ids, _ids). No mixing of styles or casing.
11 tools is well within the ideal 3-15 range for an org directory/mailbox admin server. Each tool earns its place by covering a distinct access pattern (single, batch, tree, filter, chain, settings).
The surface is entirely read-only: there is no create/update/delete for departments or users, and no update_mailbox_settings despite get_mailbox_settings existing, which is a notable gap for an 'Admin' server. Read coverage (single, batch, tree, filter, chain, shared accounts, mailbox settings) is otherwise solid.