A
licenseNot graded
qualityD
maintenanceAn 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.
11 npm
MIT
gdocs-mcp
by dasasian
Related Servers
Alternatives to gdocs-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to interact with Google Docs, Sheets, and Drive using the user's own Google account.-
- 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.20 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA powerful Model Context Protocol (MCP) server implementation for seamless Google Docs API integration, enabling AI assistants to create, read, update, and manage Google Docs.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI assistants to manage Google Docs through natural language, including listing, reading, creating documents, and appending text. It features a simple browser-based OAuth login and persistent sessions.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP (Multi-Agent Conversation Protocol) Server that enables AI agents to interact with Google Docs via natural language, automatically generated using AG2's MCP builder.-
TDQS
A3.9/5.0
Scored across 32 tools
Disambiguation5/5
Every tool targets a distinct action or resource: read/write pairs (get_style/set_style), content operations (edit_doc, insert_content, overwrite_doc) are clearly differentiated, table style vs structure tools are separate, and sharing/tab/drive tools are unique. No two tools appear to do the same thing.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern (get_, set_, list_, read_, edit_, insert_, export_, overwrite_, share_, etc.). The only exception is 'drive' but it's a command-style tool; all others are predictable and consistent.
Tool Count2/5
32 tools is well above the typical well-scoped range (3-15). While the server covers many aspects of Google Docs, the sheer number, including many read/write pairs, makes the surface feel bloated; many tools could be consolidated or the scope narrowed.
Completeness4/5
The tool set is nearly comprehensive for document management: create, read, edit, style, insert, export, suggestions, comments, permissions, tabs, and Drive navigation are all covered. However, there is no delete_doc tool (Drive explicitly has no rm), leaving a notable gap in lifecycle coverage.
Maintenance
ActivityMaintained
ResponsivenessWithin a week