Skip to main content
Glama
TheMossConcept

Gmail Sender MCP Server

by TheMossConcept
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Gmail Sender MCP Server

No user-submitted related servers found.

    Related Servers

    • Gmail MCP Server

      adel-noufal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables listing recent emails, creating drafts, and sending emails through Gmail with a required approval token for send operations.
      1
      MIT

    • email-mcp

      pavankrishna813
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables searching contacts, drafting, and sending emails via the Gmail API with explicit user approval required before sending.
      25 npm
      ISC

    • Gmail MCP Server

      faithk7
      A
      license
      B
      quality
      D
      maintenance
      Enables comprehensive Gmail management including sending, reading, and organizing emails, managing labels, drafts, threads, and configuring account settings through the Gmail API with secure OAuth2 authentication.
      64
      1,157 npm
      MIT

    • gmail-mcp-server

      ganeshhgupta
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables sending Gmail messages through the Gmail API, including optional attachments, CC/BCC, and HTML bodies, with no mailbox read access.
      -

    • Gmail MCP

      HitmanLy007
      A
      license
      C
      quality
      D
      maintenance
      Enables comprehensive Gmail management through the Gmail API, including sending/receiving emails, organizing labels and threads, managing drafts, and configuring account settings with secure OAuth2 authentication.
      64
      1,157 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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: creating a draft vs sending an email. An agent can easily differentiate between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern using camelCase (createDraft, sendEmail), demonstrating strong naming consistency.

    Tool Count5/5

    With only 2 tools, the server is tightly scoped to its purpose of sending emails and creating drafts. Each tool earns its place.

    Completeness3/5

    The server covers core email sending and draft creation but lacks common operations like listing, deleting drafts, or managing attachments. There are notable gaps for a full workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources