Skip to main content
Glama
Vinksj

gmail-multi-mcp

by Vinksj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gmail-multi-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -

    • gmail-mcp

      Bloody-Regina
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting Gmail to MCP clients, allowing search, read, send, reply-all, forward, attachments, drafts, labels, and thread management across multiple Google accounts at once via a self-hosted Cloudflare Worker.
      MIT

    • 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

      Nicolasza1973
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Gmail to AI assistants via the MCP protocol, enabling search, read, send, and manage emails across multiple Google accounts simultaneously.
      MIT

    • multi-account-gmail-mcp

      zack-bolich
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server for managing multiple Gmail accounts with separate OAuth grants, supporting search, retrieval, labels, drafts, and attachments while deferring direct send and destructive actions for safety.
      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.7/5.0

    Scored across 22 tools

    Disambiguation5/5

    Every tool targets a distinct action and resource (accounts, threads, messages, drafts, labels, attachments). There is no ambiguity between similar operations like trash_thread vs trash_message or label_thread vs label_message, as the descriptions clearly differentiate the scope.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_draft, list_labels, send_message). The verbs are clear and uniform, making the tool set predictable for an agent.

    Tool Count4/5

    With 22 tools, the server covers the core Gmail API surface comprehensively, including account management. While this is above the typical 3-15 range for a well-scoped server, each tool serves a distinct purpose and the count is justified by the multi-account complexity.

    Completeness4/5

    The tool set covers CRUD operations for threads, messages, drafts, and labels, plus search, attachments, and account management. Minor gaps exist (e.g., no explicit mark-as-read or spam tools), but these are handled indirectly through labeling and the core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources