Skip to main content
Glama
gmail-drafts-mcp

gmail-drafts-mcp

Related Servers

Alternatives to gmail-drafts-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search, read, and draft replies to Gmail messages and threads using least-privilege OAuth access, while never sending, deleting, labeling, or archiving mail.
      4
      119 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and reading Gmail messages, listing labels, and creating email drafts without sending or deleting emails.
      119 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to search, read, draft, and send Gmail messages, as well as manage labels and trash using natural language.
      24
      482 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read unread Gmail messages and create threaded draft replies, without ever sending email automatically.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Gmail by reading unread emails with automatic classification, creating AI-generated draft replies, and saving drafts directly to Gmail through the Gmail API.
      119 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Gmail through OAuth2 authentication, allowing users to list, search, read emails, and create drafts with a safety-first design that prevents accidental sends by default.
      119 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct action-resource pair: search the mailbox, read one message by uid, create a draft, list labels. There is minor conceptual proximity between gmail_search and gmail_labels, but the descriptions make the boundary clear (label enumeration vs. message querying).

    Naming Consistency5/5

    All four tools follow a uniform snake_case gmail_<verb>|noun pattern (gmail_search, gmail_read, gmail_draft, gmail_labels). No mixed conventions or vague verbs.

    Tool Count4/5

    Four tools is lean but defensible for a narrowly scoped draft-oriented Gmail server: search, read, draft, labels cover the core loop. It edges toward thin since there is no tool to inspect or manage existing drafts.

    Completeness3/5

    The search → read → draft workflow is closed and send is deliberately omitted, but draft lifecycle is incomplete: no listing, updating, or deleting of existing drafts, so an agent can create duplicate drafts with no way to check. gmail_read surfaces attachment metadata but there is no way to fetch attachment content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues