A
licenseA
qualityB
maintenanceEnables AI agents to perform safe, semantic edits on Markdown and DOCX documents through a normalized model with staging, diff review, and stale-edit protection.
13
MIT
google-docs-mcp
by dbuxton
Related Servers
Alternatives to google-docs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to make real in-place edits to Google Drive files—preserving file IDs, revision history, comments, and sharing—while also supporting appends, targeted find-and-replace, reads, searches, and file creation.MIT
- FlicenseNot gradedqualityCmaintenanceEnables reading, editing, and rewriting Google Docs documents with tools that support full content replacement, appending, heading-based insertion, and style-preserving rewrites.-
- FlicenseAqualityCmaintenanceEnables AI agents to create and edit Google Docs and draft Gmail emails through natural language.7-
- AlicenseAqualityBmaintenanceLets 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.210MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to efficiently manage and update component documentation with precise partial updates, saving up to 75% tokens compared to full rewrites.ISC
TDQS
A3.9/5.0
Scored across 14 tools
Disambiguation4/5
Most tools target clearly distinct actions: insert before/after, append, delete paragraph, search/replace, and comment operations are easy to tell apart. The only mild ambiguity is between docs_search_replace and docs_batch_replace, since batch replace is a superset of single replace, though their descriptions clarify the intended use.
Naming Consistency4/5
All tools share a consistent docs_ prefix and use clear snake_case verb patterns. Minor deviations like docs_get vs docs_read_comments and compound verbs like search_replace and batch_replace keep naming predictable but not perfectly uniform.
Tool Count5/5
14 tools is well within the ideal range for a document-centric MCP server. Each tool covers a distinct operation, from document lifecycle to paragraph editing and comment management, without feeling bloated or redundant.
Completeness4/5
The toolset covers the main workflows: create, list, read, edit paragraphs, search/replace text, and full comment lifecycle. Minor gaps exist around document deletion, copying, exporting, and formatting control, but agents can accomplish most typical Google Docs tasks without dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues