Skip to main content
Glama
MCPEmails

MCPEmails

Related Servers

Alternatives to MCPEmails

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.
      17 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search, read, send, reply to, organize, and bulk-delete email across multiple IMAP/SMTP mailboxes, with connection pooling and AES-256-encrypted credential storage. Supports 15+ providers through a web-based setup wizard and works with Claude, Cursor, and any MCP client.
      1,035 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provider-agnostic email MCP server that connects any IMAP mailbox to AI assistants, enabling email management through natural language.
      8
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Give Claude (or any MCP client) a real email inbox and SMS. Your AI agent can read and send email, manage inboxes, track delivery, and handle SMS.
      27
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects existing IMAP/POP3/SMTP email accounts to AI assistants via MCP, with a web client for managing accounts and downloading attachments.
      4 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search, read, send, reply to, forward, organize, move, and bulk-delete email across multiple IMAP/SMTP mailboxes, with AES-256-encrypted credential storage, connection pooling, and folder management. Supports 15+ pre-configured providers and works with any MCP client such as Claude or Cursor.
      1,035 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools are clearly separated by resource (inbox, email, folder, draft, schedule, signature, automation, contact, approval, bulk). The main ambiguity is email_organize vs email_search_and_move, but the descriptions explicitly call out the distinction (id-based vs filter-based), and email_delete vs bulk_execute are also clearly separated by destructive scope.

    Naming Consistency4/5

    Tool names mostly follow a noun_verb or verb_noun pattern (inbox_list, email_read, email_organize, folder_list, draft_list, signature_get, automation_read, contact_search, approval_review, bulk_execute). Minor deviations: 'folder' and 'draft' are bare nouns for CRUD tools, and 'schedule' is a verb while 'schedule_list' is noun_verb, but the pattern is still readable and predictable.

    Tool Count4/5

    23 tools is on the higher end but justified for a full email server covering inboxes, messages, folders, drafts, scheduling, signatures, automations, contacts, approvals, and bulk operations. Each tool has a distinct role, though a few could be merged (e.g., approval_review/decide/update/schedule could be one tool with actions).

    Completeness5/5

    The surface covers the full email lifecycle: read, search, compose, send, reply, forward, organize, delete, drafts, scheduling, signatures, folders, automations, contacts, approvals, and bulk operations. The only minor gap is no direct tool for listing sent mail, but email_read with folder='Sent' covers that.

    Maintenance

    ActivityActive
    ResponsivenessLimited data