Gdocs Comments MCP server
io.github.stanislawherjan1/gdocs-comments-mcp·v0.1.1·3 starsAdd inline, range-anchored comments to Google Docs - the one comment op the Google APIs can't do.
3 stars42 downloads/wk
Reviews
Write oneNobody has reviewed Gdocs Comments yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gdocs Comments tools (2)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
add_commentAdd an inline comment anchored to a specific text fragment in a Google Doc
check_connectionCheck whether the Google session behind this server is usable: launches/attaches the browser
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 75 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Gdocs Comments compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 1,299 Productivity servers
- Tools
- 2
- the typical Productivity server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 3
- more than 65% of 854 Productivity servers
- Downloads a week
- 42
- more than 30% of 427 Productivity servers with a package
What its tools let an agent do: 1 read · 1 create
Install Gdocs Comments in Claude Code, Cursor or VS Code
Runs npx -y gdocs-comments-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add gdocs-comments-mcp -- npx -y gdocs-comments-mcp
What the publisher says
From the Gdocs Comments repository's README, as published. We do not edit it. Read it on GitHub
gdocs-comments-mcp
Inline, range-anchored comments for Google Docs — the one comment operation the Google APIs can't do.
= 18">
Quickstart · Scope · Tools · Configuration · How it works · Troubleshooting · Server deployment · FAQ
You're building an AI process around Google Docs — an agent that reviews drafts, audits contracts, gives editorial feedback. The natural way to deliver that feedback is how humans do it: a comment pinned to the exact sentence it's about, not a wall of text dumped at the end of the doc or into chat.
Then you hit the wall: the Google APIs can't create anchored comments. The Docs API has no comment endpoints at all, and the Drive API accepts an anchor field only to have the Docs editor ignore it — the comment shows up as a general, whole-document comment.
This MCP server closes that gap. Your agent calls add_comment with a text fragment and a comment; the server posts it through a real, logged-in Google Docs session, so it lands anchored to that exact text — just as if a human had selected it and pressed Ctrl+Alt+M:
Why not the official APIs?
This server does one thing: add a comment to a Google Doc. The interesting case is the anchored one — a comment pinned to a specific text range — which no Google API can do.
The Docs API has no comment endpoints at all. The Drive API's comments.create accepts an anchor field, but the Docs editor ignores it — the comment renders as an unanchored, whole-document comment. The editor's own anchor format (kix.*) is undocumented and can't be produced externally (Drive API docs, issuetracker #292610078, open since 2016). Driving the editor UI is the only way — so this server does exactly that, and nothing else. (Listing, replying, resolving, and deleting comments already work over the Drive API — use a Drive-based tool for those.)
What this does — and what it doesn't
This server is deliberately one narrow thing. Read this before wiring it in.
✅ It does: add comments to a Google Doc — anchored to a specific text range (the part no API can do), or unanchored on the whole document.
❌ It does NOT:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gdocs Comments: common questions
- Is Gdocs Comments MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Gdocs Comments safety report
- How do I install Gdocs Comments?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Gdocs Comments need an API key?
- No secret keys are declared. It reads 2 settings from the environment.
- Is Gdocs Comments maintained?
- The last commit was 115 days ago (2026-07-12). The latest release is v0.1.1.
- What can I use instead of Gdocs Comments?
- Servers from other publishers that do the same job: CometChat Docs MCP server, Google Drive MCP server and Context7 MCP server.
- How does Gdocs Comments compare with other Productivity MCP servers?
- safety score 88/100 (higher than 75% of 1,299 Productivity servers); tools 2 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Gdocs Comments
Same job from other publishers: the closest match first, then the best rated.
CometChat DocsCometChat docs search + implementation bundles: add chat, voice, video & moderation to your app.not reviewedGrowingA- Google Drive MCPSecure access to Google Drive, Docs, Sheets, Slides, and Calendar through MCP.not reviewedGrowingB
Context7Up-to-date docs for AI agentsnot reviewedWidely usedA
Svelte MCPThe official Svelte MCP server providing docs and autofixing tools for Svelte developmentnot reviewedEstablishedA- MCP Server for ExcelExcel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.not reviewedEstablishedA
