gdocs-comments-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GDOCS_COMMENTS_CDP_URL | No | Attach to an existing browser over CDP instead of managing a profile. | |
| GDOCS_COMMENTS_HEADLESS | No | Set false to watch the automation work. | true |
| GDOCS_COMMENTS_AUDIT_LOG | No | JSONL audit log (hashes only, no content). | |
| GDOCS_COMMENTS_PROFILE_DIR | No | Where the logged-in browser profile lives (set a different dir per Google account). | ~/.gdocs-comments-mcp/profile |
| GDOCS_COMMENTS_IDLE_CLOSE_MIN | No | Close the managed browser after N idle minutes (0 = keep open). | 10 |
| GDOCS_COMMENTS_BROWSER_CHANNEL | No | chrome | msedge | chromium (bundled; needs npx playwright install chromium). | chrome |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_commentA | Add an inline comment anchored to a specific text fragment in a Google Doc (the comment is pinned to that exact phrase, like selecting text and commenting on it by hand). USE THIS WHEN the user wants to leave feedback, notes, questions, edits, or review comments on specific passages of a Google Doc — e.g. "review this doc and comment on the weak spots", "leave a comment on that sentence", "add editorial feedback inline". This is the ONLY way to place anchored comments: the Google Docs and Drive APIs cannot anchor a comment to a text range, so this drives a real logged-in Docs session in a browser. Do NOT use for list/reply/resolve/delete — those work over the Drive API. Requires a one-time |
| check_connectionA | Check whether the Google session behind this server is usable: launches/attaches the browser and probes docs.google.com. Returns { connected, mode }. Call this to diagnose failures; if connected=false, ask the operator to run |
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 2 tools
The two tools are completely distinct: add_comment performs the core action of adding anchored comments, while check_connection is a diagnostic for session health. There is no overlap or ambiguity between them.
Both tool names follow the consistent verb_noun snake_case pattern (add_comment, check_connection), making the API predictable and easy to navigate.
With only two tools, the server is minimally scoped but fits a narrow purpose of adding anchored comments plus a connectivity check. It's slightly thin but not unreasonable for such a specific use case.
The server only supports adding comments; there are no operations to list, reply, resolve, or delete comments, which are core comment management features. This is a significant gap for a server dedicated to Google Docs comments.