Skip to main content
Glama
moz9

Universal Mail MCP

by moz9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Universal Mail MCP

No user-submitted related servers found.

    Related Servers

    • Agentic Mail Bridge

      ArgonTechSolutions
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables supervised reading, drafting, and sending of email across labeled Gmail, Google Workspace, and Purelymail accounts without a default sender, using explicit delivery authorizations and secure local credential storage.
      MIT

    • qs-gmail

      kazukiishizuka-cmd
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to search, read, send, draft, archive, and manage multiple Gmail accounts through a single stdio server, addressing accounts by short identifiers.
      MIT

    • multi-email

      lanfuli
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables safe, multi-account Gmail and Microsoft 365 operations with explicit aliases, including searching, reading, drafting, archiving, labels/categories, and human-reviewed sending via a localhost approval window.
      MIT

    • proton-mcp-server

      QinZinn
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to Proton Mail via MCP, enabling AI agents to list accounts/folders, search messages, and read emails using Proton Mail Bridge's local IMAP server.
      MIT

    • Maily MCP Server

      ThanaelFontaine
      A
      license
      Not graded
      quality
      A
      maintenance
      A local stdio MCP server that gives any MCP client one connection to all of the user's Gmail, Google Workspace and IMAP accounts at once, letting assistants list accounts, read messages and attachments, run full-text search across mailboxes, trigger syncs and export messages as .eml. It runs on the user's own computer with encrypted secrets and no intermediary server, so mail is fetched directly from the providers.
      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.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: account/folder discovery (list_accounts, check_account, list_folders), message access (search_messages, read_message), state change (mark_read), and a two-step send flow (prepare_send, send_prepared). The potentially confusable pair mark_read vs read_message is explicitly differentiated ('without setting Seen' vs 'change read/unread state').

    Naming Consistency5/5

    All eight tools follow a consistent snake_case verb_noun convention (mark_read, list_accounts, check_account, list_folders, search_messages, read_message, prepare_send, send_prepared). No mixed styles or vague standalone verbs.

    Tool Count5/5

    Eight tools is well-scoped for a mail server covering discovery, read, search, flag, and send. Each tool earns its place with no redundant or filler operations.

    Completeness4/5

    Core read and send workflows are covered end-to-end, including a safe preview/send split. However, lifecycle gaps remain: no move/delete/archive or flag/star operations, and attachment download is explicitly unsupported in v0.1.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources