Google Workspace MCP
Related Servers
Alternatives to Google Workspace MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceExposes 38 tools that let AI agents search and read Gmail, draft and send messages, find and export Drive files, and work with Sheets, Docs, Slides, Calendar, Tasks, Forms and Contacts. It routes everything through Google's official Workspace CLI, so the user's own credential is created locally and never leaves their machine.3858 npm1MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely interact with Google Workspace services, including sending emails via Gmail and appending content to Google Docs.221 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables management of Google Workspace apps (Docs, Sheets, Gmail, Calendar, Drive) from the command line via Gemini CLI.647Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and LLMs to directly access Google Workspace APIs such as Drive, Docs, Sheets, Gmail, and Calendar by executing gws CLI commands through MCP tools.2 npmGPL 3.0
- AlicenseNot gradedqualityAmaintenanceGmail, Google Calendar, Drive, Sheets, Tasks and Contacts for AI agents, using your own Google OAuth login. Runs locally over stdio with 23 tools: search and send mail, manage events, read and write Sheets, upload and share Drive files.590 PyPIMIT
TDQS
Scored across 38 tools
Most tools map cleanly to unique resource/action pairs, but tasks_lists and tasks_list differ by a single 's' while referring to different things, which is a likely misselection trap. sheets_read and sheets_get also sound like the same operation until you read the descriptions.
The dominant pattern is service_verb_noun (gmail_get_message, drive_create_folder, calendar_create_event), and it is mostly followed. tasks_lists, forms_responses, and workspace_raw/schema break the pattern, and tasks_lists vs tasks_list creates an inconsistent verb/noun collision.
38 tools is on the high side, but the server covers nine distinct Google services with small per-service sets, plus a raw API pair to cover edge cases. The count is heavy but reasonable for the stated Workspace-wide scope.
Core workflows such as Gmail search/draft, Calendar CRUD, Drive search/export, Sheets read/write/append, and Tasks create/complete are all covered. Some surfaces are read-only or append-only (Contacts, Forms, Slides, Docs), but workspace_raw and workspace_schema explicitly fill those gaps.