Gdocs Comments MCP

Name: Gdocs Comments MCP
Author: stanislawherjan1

by stanislawherjan1version 0.1.1i★ –iRuns on your computer

Registry nameio.github.stanislawherjan1/gdocs-comments-mcp

Install

Overview

Description from the maker (original English)

Add inline, range-anchored comments to Google Docs - the one comment op the Google APIs can't do.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: GDOCS_COMMENTS_PROFILE_DIR, GDOCS_COMMENTS_CDP_URL

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "gdocs-comments": {
      "command": "npx",
      "args": [
        "-y",
        "gdocs-comments-mcp"
      ],
      "env": {
        "GDOCS_COMMENTS_PROFILE_DIR": "your-value",
        "GDOCS_COMMENTS_CDP_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add gdocs-comments --env GDOCS_COMMENTS_PROFILE_DIR=your-value --env GDOCS_COMMENTS_CDP_URL=your-value -- npx -y gdocs-comments-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "gdocs-comments": {
      "command": "npx",
      "args": [
        "-y",
        "gdocs-comments-mcp"
      ],
      "env": {
        "GDOCS_COMMENTS_PROFILE_DIR": "your-value",
        "GDOCS_COMMENTS_CDP_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "gdocs-comments": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gdocs-comments-mcp"
      ],
      "env": {
        "GDOCS_COMMENTS_PROFILE_DIR": "your-value",
        "GDOCS_COMMENTS_CDP_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

GDOCS_COMMENTS_PROFILE_DIR env
Browser profile location (default ~/.gdocs-comments-mcp/profile)
GDOCS_COMMENTS_CDP_URL env
Attach to an existing browser over CDP instead of managing a profile

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account stanislawherjan1, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 2200 servers in this category
Published to the registry more recently than 18% of the other 2200 servers in this category
Basic checks equal to or better than 100% of the other 2200 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Gdocs Comments MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Add a comment…	Google Docs API	Google Drive API	this server
unanchored (whole document)	❌	✅	✅
anchored to a text range	❌	❌	✅

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:

You want to…	Use instead
Read the document's content (so an agent can decide what to comment on, or get the exact text to anchor to)	Google Docs API (`documents.get`) or a Docs-reading MCP
Export the doc (text / markdown / PDF)	Google Drive API (`files.export`)
List / reply to / resolve / delete comments	Google Drive API (`comments.*`) — faster, no browser

Important: this tool never returns document content — its output is structured-only ({ ok, anchored, occurrence_used, verified }), by design, so a malicious doc can't inject instructions into your agent. That means the agent is writing *blind*: to review a doc intelligently, pair this with a read capability (Docs API documents.get) and feed the exact quoted text back in as find_text. The two use different auth — this server drives a logged-in browser session (no OAuth), while the Docs/Drive APIs need an OAuth token or service account — but they can run against the same Google account.

Quickstart

One command — signs you in (opens a browser once), then registers the server with Claude Code:

npx -y gdocs-comments-mcp setup

That's it — skip to Use it below. Prefer to do it by hand, or use another client? The manual steps are below.

Manual setup

1. Log in once — opens a browser window; the Google session is saved to a local profile (~/.gdocs-comments-mcp/profile):

npx -y gdocs-comments-mcp login

2. Add the server to your MCP client:

# Claude Code

claude mcp add gdocs-comments -- npx -y gdocs-comments-mcp

Other MCP clients — after login, add the config for your client:

Claude Desktop / Cowork

Add to claude_desktop_config.json (Settings → Developer → Edit Config):

"mcpServers": { "gdocs-comments": { "command": "npx", "args": ["-y", "gdocs-comments-mcp"] } } }

</details>

Project-level .mcp.json (shared with your team via git)

Create .mcp.json in the project root — Claude Code, Cowork, and most MCP clients pick it up:

"mcpServers": { "gdocs-comments": { "command": "npx", "args": ["-y", "gdocs-comments-mcp"] } } }

Note: every user of the project still runs npx gdocs-comments-mcp login once on their own machine — sessions are personal and never shared through git.

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

"mcpServers": { "gdocs-comments": { "command": "npx", "args": ["-y", "gdocs-comments-mcp"] } } }

</details>

VS Code (GitHub Copilot)

Add to .vscode/mcp.json:

"servers": { "gdocs-comments": { "type": "stdio", "command": "npx", "args": ["-y", "gdocs-comments-mcp"] } } }

</details>

3. Use it — ask your agent:

Add a comment to https://docs.google.com/document/d/1AbC…/edit — anchor it to "quarterly numbers" and say "Update this before Friday".

The agent calls add_comment and gets back:

{ "ok": true, "anchored": true, "occurrence_used": 1, "verified": true }

…and the comment is sitting on the highlighted phrase in the doc, from the account you logged in with.

No Playwright browser download is needed — by default the server drives your installed Google Chrome via playwright-core.

Tools

`add_comment`

Param	Required	Description
`doc`	✅	Document id or full `docs.google.com/document/d/ /edit` URL
`comment_text`	✅	Comment body (plain text, newlines OK)
`find_text`	—	Exact, single-line text fragment to anchor to (must match the doc text). Omit to add a general, unanchored comment on the whole document.
`occurrence`	—	Anchor to the N-th match when `find_text` appears multiple times (default 1)

Returns { ok, anchored, occurrence_used, verified } — verified: true means the posted comment was observed in the page after submitting. If find_text is given but not found, the call fails with TEXT_NOT_FOUND and nothing is posted.

The tool never returns document content, so a malicious doc can't inject instructions into your agent through it.

`check_connection`

Probes the Google session; returns { connected, mode }. If connected: false, run npx gdocs-comments-mcp login again.

Scope note: this server does *one* thing — creating anchored comments. Listing, replying, resolving, and deleting comments all work fine through the Drive API (comments.*), which is faster and needs no browser — use a Drive-based MCP for those.

CLI

npx gdocs-comments-mcp login    # one-time interactive Google sign-in

npx gdocs-comments-mcp status # is the saved session still valid? npx gdocs-comments-mcp logout # delete the saved session/profile

Configuration

All optional, via environment variables:

Env var	Default	Purpose
`GDOCS_COMMENTS_PROFILE_DIR`	`~/.gdocs-comments-mcp/profile`	Where the logged-in browser profile lives (set a different dir per Google account)
`GDOCS_COMMENTS_BROWSER_CHANNEL`	`chrome`	`chrome` \	`msedge` \	`chromium` (bundled; needs `npx playwright install chromium`)
`GDOCS_COMMENTS_HEADLESS`	`true`	Set `false` to watch the automation work
`GDOCS_COMMENTS_IDLE_CLOSE_MIN`	`10`	Close the managed browser after N idle minutes (`0` = keep open)
`GDOCS_COMMENTS_CDP_URL`	—	Attach to an existing browser over CDP instead of managing a profile (see below)
`GDOCS_COMMENTS_AUDIT_LOG`	off	JSONL audit log (hashes only, no content)

Troubleshooting

Error	What it means	Fix
`NOT_CONNECTED`	No saved Google session yet	`npx gdocs-comments-mcp login`
`SESSION_EXPIRED`	The saved session lapsed (idle sessions die after ~1–2 weeks)	`npx gdocs-comments-mcp login` again
`TEXT_NOT_FOUND`	`find_text` doesn't occur in the doc (or `occurrence` > number of matches)	Pass a fragment that matches the doc text exactly — nothing was posted
`NO_BROWSER`	No Chrome/Edge/Chromium found	Install Google Chrome, or `npx playwright install chromium` + `GDOCS_COMMENTS_BROWSER_CHANNEL=chromium`
`PROFILE_LOCKED`	Another process holds the profile (usually a running server + a `login`/`status` attempt)	Stop one of them, or use a second `GDOCS_COMMENTS_PROFILE_DIR`
Comment lands but `verified: false`	The post-submit check couldn't see the comment (can be a false negative on long comments)	Check the doc; rerun with `GDOCS_COMMENTS_HEADLESS=false` to watch

First run on a new machine? npx gdocs-comments-mcp status tells you exactly where you stand.

Running on a server / datacenter IP

On a residential machine the default profile mode just works. On datacenter IPs, Google's anti-fraud rejects a freshly launched browser process reusing a saved session — it bounces to accounts.google.com/confirmidentifier. Relaunching from a profile does not work there.

What does work: keep the exact browser the operator logged into alive, and let this server attach to it:

Start a long-lived Chrome/Chromium (under Xvfb if headless) with --remote-debugging-port=9333 and log in to Google inside it once.
Run the MCP server with GDOCS_COMMENTS_CDP_URL=http://127.0.0.1:9333.

The server then drives that live session over CDP and never launches its own browser. Keep the session warm by navigating it to docs.google.com every few hours, or an idle session expires after ~1–2 weeks.

How it works

Because the APIs can't anchor a comment, the server does exactly what a person would: it drives the real Google Docs editor. Here's the full path of one add_comment call.

1. Attach to a logged-in browser. In the default *profile mode*, the server owns a persistent Chromium profile (your installed Google C

Only the beginning is shown; read the rest in the repo

Gdocs Comments MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

Why not the official APIs?

What this does — and what it doesn't

Quickstart

Tools

add_comment

check_connection

CLI

Configuration

Troubleshooting

Running on a server / datacenter IP

How it works

`add_comment`

`check_connection`