Skip to main content
Glama
AliMail Admin MCP

AliMail Admin MCP

by mfc-open

Related Servers

Alternatives to AliMail Admin MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1,044 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage MSP-multi-tenant email security: organizations, domains, users, licensing, features, subscription packages, and email flow reporting.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Migadu email hosting services through natural language, including creating mailboxes, setting up aliases, configuring autoresponders, and handling bulk operations efficiently.
      35
      33 PyPI
      17
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to safely interact with operations systems such as cloud inventory, runbooks, and ticketing while enforcing role-based access, JWT authentication, write confirmation, secret and PII redaction, rate limits, and audit logging.
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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).

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues