Skip to main content
Glama
blackwings-dev

gmail-multi-mcp

by blackwings-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gmail-multi-mcp

No user-submitted related servers found.

    Related Servers

    • multiGmailMCP

      santoshachari
      F
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to multiple Gmail accounts simultaneously, enabling search, read, draft, send, and reply operations with per-account permission controls.
      54
      -

    • mcp-multi-gmail

      reditelai
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI assistant to access and search across multiple Gmail inboxes simultaneously, allowing unified management of work, personal, and other email accounts through a single MCP server.
      Apache 2.0

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

    • Google Multi-Account MCP

      lukaszzychal
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude and Gemini to access and manage multiple Google accounts simultaneously across services such as Gmail, Drive, Calendar, YouTube, Sheets, Analytics, AdSense, and Fitness, with create, read, update, and delete operations. It runs locally without external intermediaries to keep account access private.
      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
    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.2/5.0

    Scored across 29 tools

    Disambiguation5/5

    Every tool maps to a distinct resource and action: search/read/draft/send/reply/label/trash for email, search/read/list/upload/share for Drive, CRUD plus free-time for Calendar, and search/get/list/create/update for Contacts. read_thread vs read_message and create_draft vs send_message are explicitly scoped to avoid confusion.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern, and drive_*, calendar_*, and contacts_* prefixes make domains predictable. Minor deviations like the bare verb "reply", the unprefixed list_labels/label_message, and the noun-phrase drive_shared_drives keep it from being perfectly consistent.

    Tool Count4/5

    29 tools is high in absolute terms, but the server covers four distinct Google services plus multi-account handling, giving each domain a reasonable 5-8 tool surface. It is slightly heavy but every tool serves a distinct purpose and none feel redundant.

    Completeness4/5

    Core workflows are well covered: Gmail has search/read/draft/send/reply/label/trash, Calendar has full CRUD and free-time search, Contacts has create/read/update/search, and Drive has search/read/upload/share/create. Minor gaps exist such as no contacts_delete, no Drive delete or folder creation, and no attachment downloading, but agents can complete most real tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources