Skip to main content
Glama
TG-Techie

apple-mail-mcp

by TG-Techie
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apple-mail-mcp

No user-submitted related servers found.

    Related Servers

    • apple-mail-mcp

      ryan-grey
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables reading, searching, composing, replying, forwarding, sending, flagging, and moving macOS Apple Mail messages through native scripting, with policy-controlled outgoing drafts and attachments.
      -

    • MCP Apple Mail

      LionSR
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Apple Mail on macOS using JavaScript for Automation (JXA). Supports reading, searching, sending, and managing emails across multiple accounts with full mailbox hierarchy support.
      5
      -

    • Mac Local Mail MCP

      lg66lgnb-sketch
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search, read, and inspect Apple Mail on macOS, including conversations and attachments. It can create new, reply, reply-all, or forward drafts, but cannot send or modify existing messages.
      MIT

    • Apple Mail MCP Server

      LeChabrax
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to read, search, send, and manage email on macOS through programmatic access to Apple Mail.
      29
      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

    A3.9/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: templates, drafts, messages, mailboxes, rules, and accounts are clearly separated. The message-related tools (search, get, update, delete, thread, attachments) each have unique purposes, and the draft tools (create/update/delete/send) are unambiguous. No two tools appear to do the same thing.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (list_templates, create_rule, get_messages, etc.), but the draft tools use a noun_verb pattern (draft_create, draft_send) and email_send_html also deviates. This inconsistency between subgroups makes the naming less predictable, though each subgroup is internally consistent.

    Tool Count4/5

    25 tools is above the typical ideal range (3-15) but still appropriate for a comprehensive mail-client server covering messages, drafts, templates, rules, mailboxes, and accounts. Each tool serves a specific purpose, and no tools are redundant, though the large count requires careful organization.

    Completeness5/5

    The tool surface covers the full lifecycle for all major domains: messages (search, retrieve, update, delete, thread), drafts (create, update, delete, send), templates (list, get, save, delete, render), rules (list, create, update, delete), and mailboxes (list, create, update, delete). There are no obvious gaps that would hinder common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources