Skip to main content
Glama
jayvee6

apple-mail-mcp

by jayvee6
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to apple-mail-mcp

No user-submitted related servers found.

    Related Servers

    • Apple Mail MCP Server

      androidua
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that lets Claude Desktop interact with Apple Mail on macOS via AppleScript. It enables listing mailboxes, searching emails, and reading email content without making network calls.
      3
      MIT

    • applemail-mcp-server

      paulo-amaral
      A
      license
      A
      quality
      C
      maintenance
      A local MCP server that lets Claude read macOS Mail.app via JXA, with tools for listing accounts/mailboxes, searching and reading messages. Read-only by default, with optional opt-in write tools for compose drafts and Apple Calendar events.
      7
      MIT

    • mail-macos-mcp

      Maxtechexplore
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to control the macOS Mail app for reading, searching, drafting, sending, and managing emails directly from Claude Desktop.
      12
      MIT

    • mail-mcp

      p-l-ta
      A
      license
      A
      quality
      A
      maintenance
      MCP server that gives Claude and other MCP hosts full access to Mail.app on macOS — search, read, send, reply, flag, move, and more across all accounts configured in Mail.app.
      24
      36 npm
      1
      MIT

    • macos-mail-mcp

      marius-cetanas
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Apple Mail that enables Claude to read, search, manage, and compose emails via AppleScript.
      20
      110 npm
      1
      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.8/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes: list_emails vs search_emails differ in scope (mailbox vs. criteria-based), and move_email vs move_matching differ in single vs. bulk. A few special-case moves (archive, junk, delete) could be seen as subtypes of move_email, but their descriptions clarify the exact target mailbox. Overall, an agent can reliably select the right tool.

    Naming Consistency4/5

    The vast majority follow a verb_noun pattern (list_emails, get_email, compose_email, create_folder, etc.). Minor deviations like move_to_junk, mark_read, and get_pending_events are still readable and verb-first, but break the strict noun-as-object convention. The inconsistency is not chaotic, only slightly mixed.

    Tool Count3/5

    At 22 tools, this sits in the 'heavy' range (16-25) per calibration. Each tool does have a defined role, covering email reading/writing, rules, bulk actions, and AI assistance, which justifies the count for a full-featured mail server. However, some specialized move tools (archive, junk, delete) and the AI suite push it toward the upper bound, making the set feel slightly bloated.

    Completeness4/5

    The surface covers core email lifecycle: list, read, search, compose, reply, move, archive, flag, mark read, delete, plus folder management and rules. Notable gaps include attachment handling (no attach or download tool) and any permanent-delete/empty-trash function. These are workable gaps—agents can still perform most typical mail workflows without dead ends.

    Maintenance

    ActivityStale
    ResponsivenessSlow

    Resources