Skip to main content
Glama
PurelyMail MCP Server

PurelyMail MCP Server

by gui-wf

Related Servers

Alternatives to PurelyMail MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with the Inbound Email API to manage domains, endpoints, and email communications. Users can send or schedule emails, manage webhooks, and retrieve email threads through natural language commands.
      14
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to register domains, manage DNS, create mailboxes, and send/receive email through typed tools.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with the ability to manage email accounts through cPanel's UAPI, enabling automated email account creation, deletion, configuration, and forwarding management.
      3
      MIT
    • 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
      31 PyPI
      17
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with the Zapmail API through natural language commands for domain management, mailbox operations, and exports to third-party platforms like Reachinbox and Instantly. Provides complete coverage of 46+ Zapmail tools with dynamic API integration and multi-workspace support.
      100
      298 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to manage MXroute email hosting in plain language through the MXroute REST API, covering domains, mailboxes, forwarders, spam filtering, DNS records, disk usage, and reseller administration with built-in read-only and destructive-action guard rails. Credentials stay in the local server's environment and are sent only to MXroute over HTTPS.
      43
      4
      MIT

    TDQS

    C2.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: users, domains, routing rules, password reset methods, app passwords, ownership proof, and account credit are clearly separated. No two tools appear to perform the same operation.

    Naming Consistency4/5

    Most tools follow a readable snake_case verb_noun pattern with consistent pluralization. Minor deviations exist in verb choices such as add_domain vs create_user, modify_user vs update_domain_settings, and check_account_credit vs get_user.

    Tool Count3/5

    Nineteen tools is somewhat heavy for an account administration surface, and the count is driven by several small resource groups. Most tools are justified, but it sits at the upper end of what feels comfortably scoped.

    Completeness4/5

    Core resources have solid coverage: users have full CRUD, domains have add/list/update/delete, and routing rules plus password reset methods have create/delete/list operations. Minor gaps exist, such as no list_app_passwords and no direct update for routing rules, though most can be worked around.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data