Skip to main content
Glama
Sign In
draft-only-google

draft-only-google

by elliothimmelfarb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to draft-only-google

No user-submitted related servers found.

    Related Servers

    • gmail-mcp-server

      Parwez0786
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to read and manage your Gmail account, including listing, searching, sending, drafting, replying to, archiving, labeling, and trashing emails via the Gmail API.
      -

    • gmail-mcp

      rollecode
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude.ai and Claude Code to read and write a single Gmail mailbox, including search, drafts, sending, and label management.
      21
      MIT

    • Gmail MCP Server

      brentdemark
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to read, search, send, and manage Gmail messages and threads through natural language.
      320 npm
      MIT

    • gmail-mcp-server

      ihiteshgupta
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, sending, searching, and managing Gmail through Claude using the official Google Gmail API.
      123 npm
      3
      MIT

    • Mariana Google MCP

      marianasmall
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to manage Gmail, Google Calendar, and Google Contacts through a safety-first interface with soft-delete protections and draft-only email capabilities. Supports multiple Google accounts with comprehensive mutation logging and mandatory manual confirmation for destructive actions.
      16
      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.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action pair (thread vs message vs draft vs event), and the descriptions explicitly cross-reference each other (search_threads points to get_thread for full bodies). The only borderline pair is get_thread vs get_message, which requires the agent to know Gmail's thread/message model, but the descriptions make the split workable.

    Naming Consistency5/5

    All 14 tools follow a strict snake_case verb_noun pattern (list_/get_/search_/create_/update_/modify_/download_). No mixed conventions or vague verbs anywhere in the set.

    Tool Count5/5

    14 tools is well within a comfortable range and each maps to a concrete Gmail or Calendar operation. The split across threads, messages, attachments, labels, drafts, events, and calendars is proportionate to the two-API scope.

    Completeness3/5

    Read/create/update lifecycle is covered for drafts and events, and send is intentionally excluded by design (draft-only). However, there is no delete_draft, no delete_event, no get_draft, and no way to modify labels on individual messages rather than threads, leaving dead ends for cleanup workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources