A
licenseNot graded
qualityC
maintenanceA lightweight MCP server for managing Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Slides) through natural language with AI assistants like Claude and Cursor.
12 npm
1
MIT
google-workspace-mcp
Related Servers
Alternatives to google-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
- FlicenseBqualityDmaintenanceA server that enables Cursor users to view, create, and manage Google Calendar events through natural language commands using the MCP protocol with Google OAuth2 authentication.5-
- FlicenseBqualityCmaintenanceMCP server providing full Google Workspace access (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts) using your own OAuth credentials, enabling natural language management of Google services.100-
- FlicenseNot gradedqualityDmaintenanceA locally-hosted MCP server that integrates Gmail, Google Calendar, and Google Drive to provide AI-powered management of emails, events, and files. It enables tool-based interactions like sending emails, creating calendar events, and searching Drive files through clients like Cursor and Claude Desktop.-
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI agents to Google Workspace (Gmail, Calendar, Drive, Docs, Sheets, and Slides).302MIT
TDQS
B3.1/5.0
Scored across 58 tools
Disambiguation4/5
Tools are clearly organized by service with distinct actions. While some pairs like sheets_getText vs sheets_getRange or drive_search vs sheets_find could be confusing, their descriptions adequately clarify the intended use.
Naming Consistency3/5
Most tools follow a service_verbNoun pattern, but casing is inconsistent: some use all lowercase (e.g., drive_search, calendar_list) while others use camelCase (e.g., drive_findFolder, calendar_listEvents). This inconsistency reduces predictability.
Tool Count2/5
With 58 tools, the server is significantly over the typical 3-15 range. While the broad Google Workspace scope justifies many tools, the count is still excessive and could be streamlined, such as merging the three separate time_* tools into one.
Completeness3/5
Core workflows for Gmail, Calendar, and Chat are well covered, but Docs, Sheets, and Slides lack lifecycle operations (e.g., no create/update/delete for Sheets or Slides), and Drive lacks file upload. These gaps hinder comprehensive document and file management.
Maintenance
ActivityInactive
ResponsivenessNo issues