mcp-server-google-workspace
Related Servers
Alternatives to mcp-server-google-workspace
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables approved MCP clients to invoke read-only Google Workspace operations through typed, OAuth-scoped HTTPS interfaces while keeping Google authorization separate from MCP access.Mozilla Public 2.0
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to access and manage Google Workspace services such as Gmail, Drive, Docs, Sheets, Calendar, and Slides through the MCP protocol, with built-in OAuth 2.0 authentication and read/write tool support.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and write across Google Workspace services, including Calendar, Tasks, Gmail, Drive, Docs, Sheets, and Contacts, through a unified MCP interface.3MIT
- AlicenseAqualityDmaintenanceMCP server for Google Workspace APIs - Docs, Sheets, Drive, Gmail, and Calendar. Enables reading, creating, and editing Google Docs and Sheets, managing comments, reading emails, and viewing calendar events.3417MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to inspect Google Play releases, reviews, Android vitals, and scoped bulk reports, and to prepare explicitly authorized changes using locally supplied service-account credentials. Reads are default, while optional writes and sensitive reads require explicit configuration and single-use execution.1344 PyPIAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables read/write access to Google Tasks, including listing, searching, creating, updating, deleting, and clearing tasks, from any MCP-compatible client.MIT
TDQS
Scored across 2 tools
The two tools are distinguishable by action (fetch vs. create), but both operate on a vague 'item' resource, leaving unclear what Google Workspace object is being accessed. An agent can tell them apart but may not know when either applies.
Both names follow a consistent google_verb_noun pattern (google_get_item, google_create_item). The convention is predictable and readable.
Two tools is far too thin for a Google Workspace server, which spans documents, sheets, calendar, drive, and mail. The surface feels like a stub rather than a usable integration.
Only get and create exist; there is no list, search, update, delete, or any domain-specific operation. Core lifecycle coverage is missing, forcing agents into dead ends for most Workspace tasks.