Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to google-workspace-mcp

No user-submitted related servers found.

    Related Servers

    • Google MCP Hub

      rescueahero4
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to work across several Google accounts at once, searching every Gmail inbox, reading and drafting email, browsing Drive, and checking or scheduling across multiple Calendars in a single conversation. It supports tags for grouping accounts and cross-account tasks, and only creates drafts, files, and events rather than sending anything without you.
      MIT

    • Google Multi-Account MCP

      lukaszzychal
      A
      license
      Not graded
      quality
      C
      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

    • gws-mcp

      borabicaco
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to read and, when explicitly enabled, modify Gmail, Google Calendar, and Google Drive across multiple Google Workspace accounts while defaulting to read-only access.
      1
      MIT

    • gmail-multi-mcp-server

      Seventhdd
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables connecting Claude to multiple Gmail accounts at once, allowing each tool call to target a specified mailbox for reading, sending, and managing email.
      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

    C2.6/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools are clearly separated by service and action, and the descriptions clarify overlaps like gmail_send vs gmail_draft_send or drive_file_get vs drive_search. The main confusion points are task_list vs tasklist_list and singular/plural contact tools, but these are still distinguishable with the descriptions.

    Naming Consistency3/5

    All names are snake_case and generally readable, but conventions vary between service_action (gmail_send, drive_search, calendar_list) and service_resource_action (gmail_message_get, drive_file_get, calendar_event_update). Singular/plural inconsistencies (contacts_list vs contact_get, gmail_labels_list vs gmail_label_create) and the near-identical task_list/tasklist_list reduce predictability.

    Tool Count2/5

    48 tools is very heavy for a single MCP server, even one spanning five Google Workspace services. While many tools are useful, the count is near the extreme end and includes convenience/niche tools such as task_complete, contacts_batch_get, and drive_file_link_access.

    Completeness3/5

    Gmail, Calendar, Drive, and Tasks have solid lifecycle coverage for common workflows, including create/update/delete and search/list operations. However, Contacts is essentially read-only with no create/update/delete, and there are notable secondary gaps such as Gmail label deletion/update and Calendar creation/deletion.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources