Skip to main content
Glama
emailalias

@emailalias/mcp

by emailalias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @emailalias/mcp

No user-submitted related servers found.

    Related Servers

    • PurelyMail MCP Server

      gui-wf
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI assistants with access to PurelyMail's email management API, enabling user, domain, routing, and billing management through natural language.
      82 npm
      10
      MIT

    • Migadu MCP Server

      Michaelzag
      A
      license
      A
      quality
      C
      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
      20 PyPI
      17
      MIT

    • mcp-mail-server

      dove-yang
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language email operations (send, search, read, manage) via IMAP/SMTP, with support for attachments, multiple mailboxes, and secure configuration.
      MIT

    • mcp-mail-server

      robotic-wings
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read, search, and manage email via IMAP, and send emails with attachments via SMTP, using natural language commands.
      386 npm
      MIT

    • MailMCP

      moellerm1968
      A
      license
      A
      quality
      D
      maintenance
      Enables reading, sending, and managing emails via IMAP/SMTP through natural language, including listing folders, searching, moving emails, and sending attachments.
      8
      5 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 13 tools

    Disambiguation5/5

    Every tool targets a distinct resource or action: aliases, display names, destinations, domains, sending, and monitoring are cleanly separated. The potential overlap between update_alias and update_alias_display_name is explicitly disambiguated, and list_email_logs vs list_exposure_events serve clearly different purposes.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (list_aliases, create_alias, delete_destination, send_email). Minor inconsistencies exist: get_dashboard_stats breaks the list_* convention, and add_destination vs create_alias use different verbs for the same kind of operation.

    Tool Count5/5

    13 tools is well-scoped for an email alias management server. Each tool covers a meaningful part of the lifecycle without redundant or filler operations, and the count sits comfortably in the ideal range.

    Completeness5/5

    The server covers the full alias lifecycle (create, list, update, delete) plus display-name-specific updates, destination management, sending, and monitoring (stats, logs, exposure alerts). No obvious dead ends or critical missing operations for the core domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources