📡 MCP Radar

stanislawherjan1/gdocs-comments-mcp

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.

3 stars
0 forks
JavaScript
momentum ▲ 6.0
created 2026-07-12
on radar since 2026-07-14
ai-agentsanchored-commentsbrowser-automationclaudeclaude-codecursordocument-reviewgdocsgoogle-docsgoogle-workspaceinline-commentsmcpmcp-servermodel-context-protocolplaywright
View on GitHub ↗

About gdocs-comments-mcp

Inline, range-anchored comments for Google Docs — the one comment operation the Google APIs can't do.

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 addcomment 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:

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 ❌ ❌ ✅

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/stanislawherjan1--gdocs-comments-mcp.html)

Related MCP servers

12122J/mcpvet

MCP security scanner — vet a Model Context Protocol server before you add it to Claude Code, Cursor, or Windsurf. Grades it A–F, catching credential theft, tool-poisoning, and install-script payloads

⭐ 10JavaScript
OneInterface/stormy-cookbook

Open-source cookbook for the Stormy Social Data API and MCP server (Model Context Protocol) — one REST API for the TikTok API, YouTube API, Instagram API, LinkedIn API, X (Twitter) API and Reddit API.

⭐ 72
aka-kika/hig-mcp

MCP server serving Apple Human Interface Guidelines as structured design tokens for AI coding agents — post-WWDC25 system colors, Liquid Glass constraints, SwiftUI mappings.

⭐ 31Python
alexpilotto/uxon-ai

MCP server and Claude skills for PPC landing pages, A/B experiments, and first-party conversion tracking. Build Google Ads and Meta pages, run cross-domain experiments, and pull CRO reports via the UX

⭐ 23
chris-asmussen/warden

One MCP server that fronts many MCP servers + Skills behind a small tool set and routes to the best one, keeping an agent's context tiny. Migrate your Claude Code MCPs/skills behind it.

⭐ 10Python
hoangann2000/figma-mcp-console

MCP server that lets your AI assistant read and write Figma in real time — no API token, no rate limits. Works with Claude, Cursor, Copilot, Codex and any MCP client.

⭐ 9Go

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.