Skip to main content
Glama
TheSameAbramovych

qmailing MCP server

by TheSameAbramovych
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to qmailing MCP server

No user-submitted related servers found.

    Related Servers

    • mcp-imap

      andrewmalov
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with email accounts via IMAP and SMTP, supporting mailbox listing, email search, retrieval, sending, and management.
      MIT

    • Mail MCP Server

      martinzarfl
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.
      16
      17 npm
      1
      MIT

    • MCP Email

      gaddobenedetti
      F
      license
      B
      quality
      D
      maintenance
      Enables AI agents to send and receive emails via POP3 and SMTP, with tools for polling, reading, deleting, and sending emails.
      5
      1
      -

    • Mail Agent MCP

      SinoEdwards
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to securely interact with Gmail and QQ Mail, including IMAP search/read/organization, attachments, and preview-confirmed sending.
      41
      1
      MIT

    • MCP Email

      voiesdegypte
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read, send, organize, and search emails across multiple IMAP/SMTP mailboxes.
      1,579 npm
      MIT

    • phison-mail-mcp

      Kinolian1107
      F
      license
      B
      quality
      D
      maintenance
      Enables AI models to send, receive, search, and manage emails via SMTP/IMAP, including support for attachments, contacts, and advanced search.
      18
      -
    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.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose (e.g., create mailbox vs. list mailboxes, get email vs. list emails, webhook CRUD separated). Descriptions further reduce ambiguity, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent 'qmailing_verb_noun' pattern in snake_case (e.g., create_mailbox, list_webhooks, send_email). No mixed conventions or vague verbs.

    Tool Count5/5

    12 tools is within the ideal range for an email service, covering mailbox management, email operations, domain config, and webhooks. Each tool has a clear role.

    Completeness4/5

    Core workflows (mailbox CRUD except delete, email send/read, domain DNS info, webhook lifecycle) are covered. Notable gaps: no delete/update mailbox, no mark read/move email, no mute sender tool. These minor gaps agents can work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources