Skip to main content
Glama
Albretsen

MCP Emails

by Albretsen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Emails

No user-submitted related servers found.

    Related Servers

    • anymail-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects any IMAP/SMTP mailbox to AI agents via MCP, enabling email read, search, send, reply, and management through natural language.
      6 npm
      MIT

    • io.github.p-w-4-z/inbox-mcp

      p-w-4-z
      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
    • commune-mcp by commune-dev

      commune-mcpofficial

      commune-dev
      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

    • MailMCP

      VictorMinemu
      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.
      10 npm
      1
      MIT

    • AnyMail MCP

      MarcinWalendowski
      A
      license
      A
      quality
      A
      maintenance
      Connect all your email accounts to your AI agent — not just one. AnyMail MCP is a local MCP server that gives an agent full read/send/organize/delete access across multiple Gmail accounts at once, over IMAP/SMTP.
      26
      8 npm
      4
      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.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
    ResponsivenessNo issues

    Resources