Skip to main content
Glama
flt-sudo

gmail-mcp-server

by flt-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to gmail-mcp-server

No user-submitted related servers found.

    Related Servers

    • gmail-multi-mcp

      anaborne
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables simultaneous management of multiple Gmail accounts through MCP, allowing per-account reads and writes with verified labels and parallel search across all mailboxes.
      8 npm
      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-multi-mcp

      Vinksj
      A
      license
      A
      quality
      C
      maintenance
      Connect multiple Gmail accounts to any MCP client, enabling search, read, draft, send, label, and organize mail across unlimited accounts with local-only OAuth token storage.
      22
      8 npm
      5
      MIT

    • gmail-mcp

      alf239
      F
      license
      Not graded
      quality
      C
      maintenance
      Multi-account Gmail MCP server for reading threads, managing labels, and creating drafts across multiple Gmail accounts.
      -
    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

    A4.6/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool targets a distinct action-resource pair: account management, search/read, send/reply/draft, labels, and trash are cleanly separated. Even similar tools like get_message and get_thread are clearly scoped by resource type, and list_labels explicitly feeds modify_labels without overlap.

    Naming Consistency5/5

    All tools use the consistent gmail_verb_noun pattern with snake_case, making the action and target predictable. Minor variation like reply_to_thread instead of reply_thread does not break the overall convention.

    Tool Count5/5

    Twelve tools is well-scoped for a Gmail server: account lifecycle, search/read, send/reply/draft, labels, and trash each get focused coverage without redundancy. The count is solidly within the ideal range.

    Completeness4/5

    Core Gmail workflows are well covered: search, read, send, reply, draft, label modification, trash, and multi-account management. Minor gaps exist—no attachment content download, no draft editing/deletion, and no label create/delete—but these are workable and do not leave the main workflows dead-ended.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources