Skip to main content
Glama
santoshachari

multiGmailMCP

by santoshachari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to multiGmailMCP

No user-submitted related servers found.

    Related Servers

    • Gmail Multi-Inbox MCP Server

      tszaks
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage multiple Gmail accounts simultaneously with built-in OAuth authentication, supporting email reading, sending, drafts, labels, and account management.
      60
      51 npm
      3
      MIT

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

      erikknave
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to access multiple Gmail/Google Workspace accounts for searching and reading mail, calendars, and attachments.
      -

    • gmail-mcp

      DavidVinu
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and draft emails across multiple Gmail accounts at once, with strict safeguards that prevent sending, deleting, or modifying mailbox settings.
      253 npm
      AGPL 3.0

    • gmail-mcp

      pouyanafisi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Gmail accounts programmatically, including sending emails, managing labels, creating filters, and handling attachments via OAuth2 authentication.
      47 npm
      4
      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 54 tools

    Disambiguation5/5

    Tools are clearly separated by domain-specific prefixes (gmail_, calendar_, chat_, drive_), making each tool's purpose immediately identifiable. Within each domain, operations are distinct, and descriptions provide enough detail to differentiate similar actions like gmail_delete vs gmail_trash or gmail_star vs gmail_unstar.

    Naming Consistency5/5

    All tool names follow a consistent 'domain_verb_noun' pattern (e.g., gmail_send, calendar_list_events). While verbs like 'read' and 'get' are used for different actions, they are contextually appropriate and not confusing.

    Tool Count4/5

    With 54 tools, this server is large but justified by covering four distinct Google services. Some tools like gmail_star/unstar or mark_read/unread could be combined, but the count is still reasonable for a comprehensive multi-service MCP.

    Completeness5/5

    The tool set provides extensive coverage for Gmail, Calendar, Chat, and Drive, including CRUD operations, search, attachments, and more. Only minor gaps like drive update file exist, but core workflows are fully supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources