Skip to main content
Glama
weirdapps

sch-mail

by weirdapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to sch-mail

No user-submitted related servers found.

    Related Servers

    • imap-smtp-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes any IMAP mailbox and SMTP relay as MCP tools, enabling email management (read, search, send, delete) through MCP-compatible agents.
      1
      MIT
    • Aspose.Email Cloud MCP Server by aspose-cloud

      Aspose.Email Cloud MCP Serverofficial

      aspose-cloud
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables reading, converting, and managing email messages, calendars, and contacts, along with mail account folder/thread operations and personal name parsing/formatting, via typed MCP tools.
      -

    • MailOKF MCP

      pat229988
      A
      license
      C
      quality
      B
      maintenance
      A local-first Python MCP server that turns Gmail, Outlook/Microsoft 365, iCloud Mail, and generic IMAP/SMTP mailboxes into a synchronized, searchable OKF knowledge layer, exposing 38 tools and four resources for mailbox actions, synchronization, retrieval, attachments, and optional semantic search while keeping the provider mailbox authoritative.
      38
      1
      MIT

    • Gmail MCP Server

      cristip73
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Gmail through the MCP protocol, supporting sending, reading, searching, replying, forwarding, managing drafts and labels, and saving attachments.
      12 npm
      3
      MIT

    • jmap-mcp

      mikluko
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server exposing JMAP email and Sieve script operations as tools, enabling mailbox management, email creation, search, flagging, and Sieve script management.
      2
      -
    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 10 tools

    Disambiguation5/5

    Each tool targets a distinct action on the mail domain: listing, searching, reading, sending, forwarding, moving, downloading attachments, folder listing/creation, and stats. The closest pair (sch_list_mail vs sch_search_mail) is clearly separated as browse-vs-query, and both share the same UID semantics, so there is no realistic misselection.

    Naming Consistency4/5

    The set follows a consistent sch_<verb>_<noun> pattern (sch_list_mail, sch_get_mail, sch_send_mail, sch_move_mail, sch_create_folder). The only deviation is sch_mail_stats, which puts the noun before the description rather than using a verb, but it remains readable.

    Tool Count5/5

    Ten tools is a well-scoped size for an email client surface, covering reading, sending, organizing, and attachments without bloat. Every tool earns its place and none appears redundant.

    Completeness3/5

    Core lifecycle is covered (list, search, read, send, forward, move, create folder, attachments, stats), but notable operations are missing: no delete_mail or delete/rename folder, and no reply or mark read/unread. These are common email workflows whose absence forces agents to work around dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources