Skip to main content
Glama
Sign In
gmail-mcp

gmail-mcp

by DimitrisPasakaleris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gmail-mcp

No user-submitted related servers found.

    Related Servers

    • Gmail MCP Server

      Paviyarasanmani
      A
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server that gives Claude full Gmail control — send directly, read, reply, search, label, and delete emails.
      128 npm
      MIT

    • mcp-gmail

      knowledgeislands
      A
      license
      B
      quality
      F
      maintenance
      MCP server that connects Claude with Gmail to read, send, delete, and manage messages and labels via the Google Gmail API.
      3
      MIT

    • Gmail MCP Server

      jsflax
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides Claude with access to your Gmail, featuring a full OAuth 2.1 authorization server with dynamic client registration and tools to list, read, search, send, reply, draft, archive, trash, manage labels, and download attachments.
      280 npm
      1
      MIT

    • Gmail MCP Server

      stevesimpson418
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that provides tool-level access to Gmail, allowing Claude to search, read, send, and manage emails using the Gmail API.
      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.6/5.0

    Scored across 25 tools

    Disambiguation3/5

    The singular/batch pairs (read_email vs read_emails, archive_email vs archive_emails, etc.) are mostly distinguishable through descriptions and choice hints, but the read/search/save cluster is crowded: list_emails, read_email, read_emails, read_emails_full, search_and_save, and append_emails overlap conceptually. An agent can usually choose correctly, but several tools require careful reading to avoid misselection.

    Naming Consistency4/5

    Most tool names follow a predictable snake_case verb_noun pattern, with clear singular/plural batch variants. Minor deviations exist, such as mark_emails_read (awkward ordering) and read_emails_full, but the convention is still largely consistent.

    Tool Count3/5

    25 tools is at the heavy end for a Gmail server. Many batch variants earn their place, but some duplication (multiple read/save tools plus singular/batch pairs) suggests the surface could be consolidated.

    Completeness4/5

    The server covers core email workflows: search/list, read, send, reply, draft CRUD, archiving, trashing, labels, mark-read, attachment listing/downloading, and batch operations. Minor gaps include no batch remove_label, no create/list custom labels, and no mark-unread or permanent-delete operation, but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources