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.
14 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.22 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.14 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
A4.1/5.0
Scored across 19 tools
Disambiguation4/5
Most tools target clearly distinct resources or actions: document reading, snippet editing, comments, suggestions, permissions, page setup, and Drive navigation are well separated. The main potential confusion is between write_doc and edit_doc for writing markdown, and read_doc versus export_doc, though the descriptions make the intended boundaries mostly clear.
Naming Consistency4/5
Nearly all tools use a consistent snake_case verb_noun pattern such as read_doc, edit_doc, list_comments, add_comment, and share_doc. The single noun-only tool, drive, is a deliberate command multiplexer but is the one clear deviation from the pattern.
Tool Count4/5
At 19 tools the surface is slightly heavier than the ideal compact set, but the server covers a broad Google Docs domain including editing, comments, suggestions, sharing, page setup, export, Drive navigation, and configuration. Each tool corresponds to a meaningful operation, and drive usefully bundles several filesystem commands.
Completeness4/5
The tool set covers the core document lifecycle well: create, read, edit, replace, export, comments, suggestions, sharing, page setup, images, and Drive navigation. Notable gaps remain around deleting documents, tabs, or comments and around revision history, but these are relatively minor for the main Docs workflows.
Maintenance
ActivityNo data
ResponsivenessOutdated data