A
licenseA
qualityB
maintenanceA read/write MCP server for Google Drive, Docs & Sheets with bounded reads, gated mutations, and consistent argument naming.
26
MIT
verified-googledocs-mcp
Related Servers
Alternatives to verified-googledocs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that enables AI agents to treat Google Docs like local files: read, edit, manage suggestions and comments, and work across tabs and multiple Google accounts.3237 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Docs — create, read, edit, format, and manage documents through 26 tools via the Model Context Protocol.6 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to collaborate in shared rooms with a document edited via compare-and-swap optimistic concurrency, plus a chat channel and change deltas.26 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn unofficial MCP server for Google Docs that lets large language models securely access, read, and interact with documents, enabling smarter workflows and AI-assisted editing.6 npmMIT
- 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.10034 PyPIMIT
TDQS
A4.4/5.0
Scored across 20 tools
Disambiguation4/5
Most tools have clearly distinct purposes: reading, writing, styling, commenting, tables, and export are separated cleanly. A few pairs could be confused—read_document with format='outline' overlaps find_sections, and replace_text vs replace_range_markdown both replace content—but the descriptions provide enough guidance to disambiguate.
Naming Consistency5/5
All tool names follow a consistent verb_noun (or verb_preposition) pattern in snake_case: list_tabs, read_document, replace_text, append_markdown, resolve_comment, insert_table. The naming style is uniform and predictable across all 20 tools, with no mixed conventions or vague verbs.
Tool Count4/5
20 tools is slightly above the typical well-scoped range, but the server covers several distinct sub-domains—document reading, text editing, comments, tables, and export—so the count is reasonable. It is not bloated; each tool addresses a concrete operation, though a few could be consolidated without much loss.
Completeness4/5
The toolset covers the core document lifecycle well: read tabs, find sections, replace and append content, style text, manage comments, handle tables, and export PDFs. Minor gaps exist—no delete-section or delete-table operations, no arbitrary insertion of plain text without replacement, and no tab creation/renaming—but these are not critical dead ends for typical editing workflows.
Maintenance
ActivityMaintained
ResponsivenessResponsive