Skip to main content
Glama
japan08

multi-gmail-mcp

by japan08
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to multi-gmail-mcp

No user-submitted related servers found.

    Related Servers

    • Gmail MCP Server

      Abhitkumar89
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI assistants send, read, and manage Gmail through natural language, including email sending, inbox management, and template-based outreach.
      132 npm
      MIT

    • gmail-multi-mcp

      dtaveeva
      A
      license
      A
      quality
      B
      maintenance
      MCP server that gives an AI assistant simultaneous access to multiple Gmail accounts with per-account read-only, draft, or send tiers, two-phase write confirmation, and safeguards for handling untrusted email content.
      10
      7 npm
      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.
      -

    • Gmail MCP Gateway

      systheno
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents full read and organizational access to multiple Gmail accounts — and no ability to send, trash, or delete mail.
      MIT

    • mcp-email-client

      rifkyfadillah404
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for email management that enables reading, searching, drafting, replying to, and sending emails with thread-aware replies and draft-first safety, supporting Gmail API and IMAP/SMTP backends.
      3 npm
      -
    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

    C2.9/5.0

    Scored across 42 tools

    Disambiguation2/5

    Every tool appears twice with and without the 'multi_gmail_' prefix, making it hard for an agent to distinguish which version to call. Additionally, 'fetch_sent' is deprecated but still present, causing overlap with the more general 'fetch' tool.

    Naming Consistency2/5

    The tool naming is inconsistent due to the dual prefixes. While each group individually follows a verb_noun pattern, the coexistence of unprefixed and 'multi_gmail_' prefixed tools violates consistency and suggests redundancy.

    Tool Count2/5

    With 42 tools, the count is inflated because of deliberate duplication. The actual unique tool set is about 21, which would be appropriate for a Gmail MCP, but the duplication makes the tool surface unnecessarily large and confusing.

    Completeness4/5

    The unique tool set covers essential Gmail operations: fetch, read, send, draft, archive, follow-ups, account management, and diagnostics. Minor gaps exist (e.g., no delete or label management), but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources