Google Workspace MCP Server
Related Servers
Alternatives to Google Workspace MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to search, read, and compose Gmail, manage Drive files and Google Docs/Sheets/Slides, handle Calendar events and Tasks, and access Forms and Contacts using the official Workspace CLI, with credentials staying on the user's machine.38234 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control Google Workspace services (Slides, Docs, Sheets, Drive) with granular tools and provides a universal CLI escape hatch for all Workspace APIs.MIT
- AlicenseBqualityDmaintenanceConnects AI assistants to Google Workspace (Gmail, Drive, Docs, Sheets, Slides, Calendar, Tasks, Forms, Chat, Contacts) through your own OAuth app, providing around 120 tools for managing email, files, calendar, and more.100MIT
- AlicenseNot gradedqualityBmaintenanceTurns Google Workspace into 45 MCP tools spanning Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat, Tasks and Contacts, with server-side OAuth and a single bearer token so any AI client can read, send, create, and manage workspace content without a browser or Google SDK.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely interact with Google Workspace services, including sending emails via Gmail and appending content to Google Docs.396 npmMIT
- AlicenseAqualityAmaintenanceExposes a curated set of Google Workspace CLI operations as tools for managing Drive, Sheets, Calendar, Docs, and Gmail. It provides a focused set of high-value operations to avoid context window bloat while enabling file management, spreadsheet updates, and email interactions.61705 npm10MIT
TDQS
Scored across 38 tools
Tools are cleanly separated by service prefix (gmail_, drive_, sheets_, docs_, calendar_, tasks_, slides_, forms_, contacts_) and each has a distinct action. Overlapping-looking pairs like drive_get_file vs drive_export and gmail_create_draft vs gmail_send_draft are explicitly disambiguated in their descriptions. An agent can reliably pick the right tool.
A consistent service_action snake_case pattern dominates (gmail_search, drive_search, sheets_read, calendar_create_event, workspace_raw). Minor deviations exist: tasks_lists vs tasks_list use confusing plural/singular forms, and gmail_modify_labels uses a different verb style, but overall it stays readable.
38 tools is heavy in absolute terms but spread across ~10 distinct Google products, averaging only ~4 per service, so each tool earns its place. The breadth of Workspace justifies the count, though it sits above the ideal range and could be trimmed.
Broad lifecycle coverage across Gmail, Drive, Sheets, Docs, Calendar, Tasks, Slides, Forms and Contacts, plus workspace_raw/workspace_schema as an escape hatch. Gaps remain (e.g. no docs content edit, no tasks update/delete, no gmail message delete, Drive only trashes), but the raw API tool lets agents work around them.