F
licenseB
qualityD
maintenanceMCP server providing full access to Google Workspace services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using OAuth authentication.
100
1
-
google-workspace-mcp-server
by EveryInc
Related Servers
Alternatives to google-workspace-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProduction-ready MCP server for Google Workspace providing broad coverage across Gmail, Drive, Calendar, Docs, Sheets, and more, with safe-by-default write operations and markdown-to-Google-Docs support.10024 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Gmail, Google Drive, and Google Calendar — search, read, send, and manage threads, files, and events.26 npmMIT
- AlicenseBqualityDmaintenanceAn MCP server for automating Google Workspace applications including Sheets, Apps Script, Drive, Docs, and Gmail. It enables users to manipulate spreadsheets, edit scripts, manage files, and send emails directly from conversational AI interfaces.31MIT
- AlicenseBqualityAmaintenanceGoogle Workspace MCP Server12174,893 PyPI3,215PythonMIT
- AlicenseNot gradedqualityBmaintenanceA set of five independent MCP servers for Google Workspace (Gmail, Calendar, Drive, Sheets, Docs) enabling secure access and management of email, calendar events, files, spreadsheets, and documents. Features OAuth 2.1 with per-resource tokens and uses stable Google product APIs.MIT
TDQS
A3.9/5.0
Scored across 34 tools
Disambiguation5/5
Each tool is clearly scoped to a specific Google Workspace service and action. The service prefixes (calendar_, docs_, drive_, gmail_, sheets_) combined with distinct verbs (e.g., create vs list vs get) ensure no two tools have overlapping purposes. For example, calendar_freebusy_query is distinct from calendar_list_events, and sheets_append_values is distinct from sheets_update_values.
Naming Consistency5/5
All tool names follow a consistent pattern: service_verb_noun in lowercase with underscores. Examples include calendar_list_events, sheets_create_spreadsheet, and gmail_get_message. There are no deviations like camelCase or mixed conventions, making the naming predictable and easy to parse.
Tool Count4/5
With 34 tools across five distinct services, the count is on the higher side but still reasonable for a comprehensive Google Workspace integration. Each service has a manageable number of tools (6-12), covering essential operations without being unnecessarily bloated. However, the total could feel heavy for agents that only need a subset of services.
Completeness3/5
The tool set covers many common operations but has notable gaps. Calendar lacks create/update/delete events, Drive lacks file upload and deletion, and Gmail lacks send and modify operations. These gaps can cause agent failures when such actions are required. The surface is strong for reading and basic manipulation but incomplete for full lifecycle management.
Maintenance
ActivityInactive
ResponsivenessNo issues