Google Docs MCP
Related Servers
Alternatives to Google Docs MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables management of Google Drive files, Docs, Sheets, Slides, and Calendar events through natural language using the MCP protocol.13,437 npm221MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Docs and Sheets that enables AI assistants to read, create, edit, style, export, and collaborate on documents using local OAuth authentication.14 npm1MIT
- AlicenseBqualityAmaintenanceEnables interaction with Google Docs through typed MCP tools, supporting reading, writing, searching, and managing documents via OAuth integration.22MIT
- FlicenseNot gradedqualityDmaintenanceEnables MCP-compatible AI assistants to interact with a user's Google Drive, including listing, searching, reading, creating, updating, and deleting files, with authentication via Google OAuth.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Google Docs — create, read, edit, format, and manage documents through 26 tools via the Model Context Protocol.12 npm1MIT
- AlicenseAqualityAmaintenanceLets AI apps read and edit Google Docs in plain language, including reading as text or Markdown, making precise range-based edits, styling, working with comments, and exporting to PDF, DOCX, and other formats.27479 npmMIT
TDQS
Scored across 21 tools
Most tools map cleanly to distinct resources and actions: document lifecycle, text insertion, formatting, and search are clearly separated. The only mild ambiguity is list_documents vs. search_documents, both of which can filter by name, but their descriptions make the intended use cases clear.
The majority of tools follow a consistent snake_case verb_noun pattern, such as get_document, create_document, insert_text, and delete_text. Minor deviations like sign_out and authenticate break the strict pattern, but the overall naming is predictable and readable.
21 tools is on the heavier side, but the breadth of Google Docs functionality—auth, document CRUD, text editing, formatting, tables, lists, links, and search—justifies the count. Each tool has a distinct role, and the set does not feel padded or redundant.
The surface covers the full document lifecycle plus rich editing, formatting, search, and auth flows, with no obvious dead ends. Minor gaps exist—such as no rename, export, image insertion, or comment handling—but these are reasonable omissions for a core Google Docs MCP server.