stanislawherjan1-gdocs-commentsSAFE
MCP server for adding inline, range-anchored comments to Google Docs — the one comment operation the Google Docs & Drive APIs can't do. For AI agents (Claude, Cursor, Copilot) that review documents.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
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.
81790cc12a7cOBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add gdocs-comments-mcp -- npx -y [email protected]
Exposed tools (2)
1 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
add_comment | write | Add an inline comment anchored to a specific text fragment in a Google Doc |
check_connection | read | Check whether the Google session behind this server is usable: launches/attaches the browser |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
2. Run the MCP server with `GDOCS_COMMENTS_CDP_URL=http://127.0.0.1:9333`.
@modelcontextprotocol/sdk, playwright-core
Gates applied: no_behavioural_pass.
81790cc12a7cfull audit observations/trust-audit/mcp-server/stanislawherjan1__gdocs-comments-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | 81790cc12a7c | SAFE | B | 89 | first audit |
Questions
What is the stanislawherjan1-gdocs-comments MCP server?
MCP server for adding inline, range-anchored comments to Google Docs — the one comment operation the Google Docs & Drive APIs can't do. For AI agents (Claude, Cursor, Copilot) that review documents.
What tools does stanislawherjan1-gdocs-comments expose?
2 in total: 1 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is stanislawherjan1-gdocs-comments safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does stanislawherjan1-gdocs-comments need?
No credential environment variables were found in its source, so it appears to need none.
How does stanislawherjan1-gdocs-comments run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as gdocs-comments-mcp at 0.1.1.
How current is this page?
The grade is for one exact copy of the source (81790cc12a7c), read on 2026-10-11. The repository is watched and re-audited when it changes.