gdoc MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GDOC_BIN | No | Absolute path to the gdoc CLI binary when running from source. Defaults to 'gdoc' on PATH. | |
| GOOGLE_CLIENT_ID | No | Google OAuth client ID. Required for the remote connector with hosted OAuth callback. | |
| GOOGLE_CLIENT_SECRET | No | Google OAuth client secret. Required for the remote connector with hosted OAuth callback. | |
| ALLOWED_GOOGLE_DOMAIN | No | Restricts Google OAuth to a specific domain, e.g., 80000hours.org for organizational deployments. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connect_googleA | Connect Google Docs by opening Google's authorization page in the user's browser. Use this when gdoc reports that it is not authenticated. The bundled OAuth client is selected automatically; no terminal or copied token is needed. |
| list_filesC | List Google Docs or Sheets in Drive or a folder. |
| search_filesC | Search Drive files by name or content. |
| read_documentB | Read a Google Doc as Markdown or a Sheet as a table. Can include tabs, revisions, and inline comments. |
| document_infoB | Get document metadata, ownership, modified time, and size. |
| list_tabsB | List document tabs or spreadsheet worksheets. |
| table_of_contentsC | Extract a document heading outline with deep links. |
| list_revisionsB | List retained revisions for a document. |
| list_commentsC | List open comments, optionally including resolved threads. |
| get_commentC | Get one comment thread with full detail. |
| add_commentC | Add a document comment, optionally anchored to quoted text. |
| reply_to_commentC | Reply to a document comment. |
| resolve_commentC | Resolve a comment, optionally with a final message. |
| reopen_commentB | Reopen a resolved comment. |
| edit_documentC | Replace text or a table cell in a document. Replacement text supports Markdown formatting. |
| create_documentC | Create a Google Doc, optionally initialized from Markdown. |
| write_documentC | Replace a whole document or one tab with Markdown. |
| insert_documentC | Insert Markdown at the start or end of a document tab. |
| add_tabC | Add a tab to an existing Google Doc. |
| copy_documentC | Duplicate a document with a new title. |
| share_documentC | Share a document with an email address. |
| gdoc_cliA | Run an allowlisted gdoc command for options not covered by typed tools. Arguments are passed directly without a shell. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool targets a specific action (e.g., create, write, insert, edit for content; list, get, add, reply, resolve, reopen for comments) with clear boundaries. No two tools have overlapping purposes.
Most tools follow verb_noun pattern in snake_case (e.g., create_document, list_comments). A few like document_info and table_of_contents are noun_noun, but overall consistent and intuitive.
22 tools cover a wide range of document and comment operations without being excessive. Each tool serves a distinct purpose, well-scoped for a Google Docs integration.
Covers most CRUD operations and commenting lifecycle, but missing a delete_document tool. Also lacks undo or restore revision functionality, leaving a notable gap for basic document management.