A
licenseNot graded
qualityA
maintenanceEnables management of Google Drive files, Docs, Sheets, Slides, and Calendar events through natural language using the MCP protocol.
13,437 npm
221
MIT
workspace-mcp
Related Servers
Alternatives to workspace-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server integrating multiple Google Workspace services including Gmail, Calendar, Drive, Sheets, Docs, Tasks, People, Forms, and Slides, enabling users to manage emails, events, files, documents, and more through natural language.15MIT
- AlicenseBqualityDmaintenanceProvides natural language control over Google Workspace services (Calendar, Drive, Gmail, Docs, Sheets, Slides, Forms, Tasks, Chat) via MCP, with OAuth 2.1 multi-user authentication.100MIT
- AlicenseBqualityDmaintenanceEnables natural language control over Google Workspace services including Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Tasks, Chat, Contacts, Apps Script, and Custom Search via a remote MCP server hosted on Google Cloud Run.114MIT
- AlicenseNot gradedqualityDmaintenanceEnables management of Google Drive files, Docs, Sheets, and Slides through natural language using MCP, with support for file operations, search, and shared drives.5 npmMIT
- AlicenseAqualityDmaintenanceEnables natural language interaction with Google Calendar, including creating, updating, deleting events and managing recurring events through MCP.1297 npmMIT
TDQS
B3.1/5.0
Scored across 122 tools
Disambiguation3/5
Most tools name their resource and action clearly, but several overlapping boundaries exist: manage_drive_access vs set_drive_file_permissions, modify_doc_text vs batch_update_doc, and create_drive_file vs import_to_google_* can route similar work different ways. Batch variants and get-content vs download tools add further selection friction despite detailed descriptions.
Naming Consistency4/5
Nearly all names are snake_case and follow a verb_noun pattern like list_*, get_*, create_*, and manage_*, which makes the set predictable. Minor deviations such as generic send_message, get_events, create_form, and debug_* / import_to_google_* tools break the strict pattern but remain readable.
Tool Count1/5
At 122 tools, this is far beyond the 50+ extreme threshold for a single MCP server and creates a heavy context and tool-selection burden. The broad Workspace scope explains the count, but a modular split into per-domain servers would be far more appropriate.
Completeness4/5
The server covers nearly every major Workspace domain—Gmail, Calendar, Drive, Docs, Sheets, Slides, Forms, Chat, Tasks, Contacts, and Apps Script—with strong CRUD-ish coverage and batch operations. Minor gaps like Drive file delete/move, Chat message editing, and direct Apps Script trigger creation are workarounds rather than dead ends.
Maintenance
ActivityActive
ResponsivenessSyncing