F
licenseB
qualityD
maintenanceEnables AI assistants to create, read, edit, and manage Google Docs and Drive files with support for formatting, comments, tables, images, and bulk operations.
57
1
-
A1 Google Docs MCP
by A1-x-Tech
Related Servers
Alternatives to A1 Google Docs MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables reading and editing Google Docs documents, including creating documents, inserting and deleting content, formatting text, and performing find-and-replace operations through natural language.24 npm2MIT
- FlicenseNot gradedqualityCmaintenanceEnables reading, editing, and rewriting Google Docs documents with tools that support full content replacement, appending, heading-based insertion, and style-preserving rewrites.-
- AlicenseNot gradedqualityCmaintenanceEnables reading and editing Google Docs via the Docs API, including structure/outline retrieval, text export, section/range/table editing, text replacement, document creation, and raw batch updates, with dry-run previews before destructive changes.MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive interaction with Google Docs and Google Drive through AI assistants, supporting document reading/writing, rich formatting, table/image insertion, comment management, and complete file/folder operations with secure OAuth authentication.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, read, and modify Google Slides, Sheets, Docs, and Drive documents programmatically. Supports file management, content editing, and version history retrieval.1,084 npm1MIT
TDQS
A4.3/5.0
Scored across 21 tools
Disambiguation4/5
Most tools target distinct operations and the detailed descriptions make boundaries clear. The main confusable pairs are get_document vs read_document_text (both retrieve document content) and create_document vs import_markdown (both can create from markdown), but their different purposes are explicitly explained. No tools appear to do the same thing.
Naming Consistency4/5
Tool names overwhelmingly follow a verb_noun pattern like create_document, insert_text, delete_range, style_paragraph, and replace_image. The pattern is only slightly strained by get_document vs read_document_text, the slightly generic manage_comment, and the non-pattern raw_request escape hatch. There is no mixed casing or chaotic naming.
Tool Count4/5
At 21 tools this is on the heavier side, but the Google Docs domain is broad and each tool covers a genuinely distinct operation such as text insertion, range replacement, styling, tables, images, breaks, and comments. The raw_request escape hatch prevents the count from ballooning further, so the size remains reasonable.
Completeness4/5
The set covers document creation, raw and readable retrieval, tab discovery, import/export, text editing, styling, table manipulation, images, breaks, and comments. Notable gaps like document deletion, moving/sharing, and advanced table/header/footer formatting are either explicitly outside the server's stated scope or delegated to raw_request. Core document workflows are usable without dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues