Skip to main content
Glama
iXanadu

gmail-mcp

by iXanadu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to gmail-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      5 npm
      3
      MIT

    • Gmail MCP Server

      brentwpeterson
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Gmail through MCP-compatible clients to list, read, search, and send emails. It supports advanced features such as managing labels, handling threaded replies, and utilizing Gmail's native search syntax.
      10 npm
      2
      MIT

    • gmail-mcp

      RonildoBraga
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables interacting with multiple Gmail accounts through a single MCP server, supporting search, labels, drafts, and thread management with per-account OAuth.
      1
      -

    • Octomail

      zerostorypoints
      A
      license
      A
      quality
      B
      maintenance
      Enables managing multiple Gmail accounts through a single MCP server, with independent OAuth per account, supporting email read, search, labeling, drafting and sending, as well as calendar and iCal feed operations.
      41
      Apache 2.0

    • Gmail MCP Server

      fred-drake
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Gmail functionalities including listing unread emails, searching via query syntax, and managing messages through archiving or marking as read. It enables MCP clients to securely interact with and organize email data using the Gmail API.
      5
      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

    B3.1/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target clearly distinct actions or resources, such as send vs reply vs forward or get_thread vs get_message. A few boundaries are close, notably accounts_add vs accounts_auth_start and get_message vs get_thread, but the descriptions are sufficient to avoid serious misselection.

    Naming Consistency3/5

    The naming style is mixed: some tools use resource_action (accounts_list, labels_create), some use action_resource (get_attachment, get_thread), and some are bare verbs (send, reply, archive, label). Within subfamilies the naming is consistent, but across the whole set there is no single predictable pattern.

    Tool Count3/5

    23 tools is on the heavy side and falls into the borderline range for a single server. However, the count is justified by the breadth of Gmail functionality covered: accounts, labels, threads, messages, drafts, sending, and attachments.

    Completeness4/5

    The tool surface covers core Gmail workflows well: search, read, send, reply, forward, draft, label, archive, trash, and attachment retrieval. Minor gaps exist, such as no explicit mark-read/unread or message mutation beyond labels and trash, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources