No user-submitted related servers found.
Scored across 240 tools
Most tools pair a service prefix with a specific resource and action, and the descriptions are detailed enough to separate lookalikes like gmail_trash/gmail_delete or drive_read/drive_export_file. A few pairs remain easy to confuse without reading descriptions, such as tasks_list vs tasks_list_tasks and sheets_batch_update vs sheets_batch_update_values, so it is not perfect.
Naming follows a predictable lowercase snake_case `<service>_<verb>_<noun>` pattern across Drive, Calendar, Gmail, Contacts, Tasks, Sheets, Docs, and Slides. The pattern is mostly consistent and readable, though a few names like gmail_profile and drive_about are non-verb deviations, and tasks_list vs tasks_list_tasks reads awkwardly.
240 tools is far beyond a practical MCP tool surface and creates an enormous selection problem for an agent. Even though the tools map to real Google APIs, a server with 50+ tools is inherently overwhelming and should be split into per-service servers.
Within the included services, coverage is deep: there are CRUD/lifecycle operations for files, calendar events, Gmail messages, contacts, tasks, spreadsheets, docs, and slides, plus permissions, settings, watch channels, drafts, labels, and batch operations. Minor gaps remain, such as no task list update, no direct Docs/Slides delete, and no Chat/Meet/Forms coverage, so it is strong but not exhaustive for all of Google Workspace.