A
licenseB
qualityA
maintenanceGoogle Workspace MCP Server
120
35,981 PyPI
3,353
Python
MIT
Google Workspace MCP VE
by HuntsDesk
Related Servers
Alternatives to Google Workspace MCP VE
- AlicenseAqualityBmaintenancePersistent memory and task board for Claude Code. 14 tools spanning projects, tasks, sessions, and activity logs — backed by Firestore, runs on the free tier. Handoff notes survive context compaction; the next session reads the last handoff and picks up where you stopped.14MIT
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.100MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Docs — create, read, edit, format, and manage documents through 26 tools via the Model Context Protocol.12 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Drive, Docs, and Sheets — built for Claude Code. Gives Claude Code direct read/write access to Google Sheets (cell-level edits, formatting, structure), Google Docs (insert, replace, append), and Drive (search).16 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables editing existing Docs, Sheets, and Slides in place, plus commenting, sharing, moving, and exporting files with native Google URLs returned. Provides 29 tools across Drive, Docs, Sheets, and Slides, using OAuth keys kept locally in ~/.gdrive-mcp/.MIT
- AlicenseNot gradedqualityCmaintenanceRead and write Google Sheets, Docs, Drive, and Apps Script from any MCP client. 82 tools with OAuth2 auth, tested against live Google APIs.1MIT
- AlicenseNot gradedqualityBmaintenanceTurns Google Workspace into 45 MCP tools spanning Gmail, Drive, Calendar, Docs, Sheets, Slides, Chat, Tasks and Contacts, with server-side OAuth and a single bearer token so any AI client can read, send, create, and manage workspace content without a browser or Google SDK.MIT
TDQS
A3.9/5.0
Scored across 149 tools
Disambiguation5/5
Each tool has a clearly distinct purpose, with detailed descriptions that cross-reference other tools to guide correct selection. Overlapping tools (e.g., modify_doc_text vs. insert_doc_markdown) are differentiated by use case and behavior, minimizing ambiguity.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (e.g., create_doc, list_spaces, manage_event). A few outliers like debug_docs_runtime_info and start_google_auth break the pattern, but overall the naming is predictable and readable.
Tool Count3/5
The 149 tools cover a wide range of Google Workspace services, which justifies a larger set. However, this exceeds the typical well-scoped range (3-15 tools), making the server heavy but still organized enough to navigate.
Completeness5/5
The tool set offers comprehensive CRUD and lifecycle coverage for each service (Docs, Sheets, Slides, Drive, Gmail, Calendar, Tasks, Contacts, Forms, Chat, Apps Script, etc.). Only niche features like advanced animations are missing, and most common workflows are fully supported.
Maintenance
ActivityInactive
ResponsivenessNo issues