google-drive-comments-mcp

A focused Model Context Protocol server (and standalone CLI) for reading comments on Google Drive files — Docs, Sheets, and Slides. Two tools, read-only OAuth scope, no extra surface area.

Built because the hosted Google Drive connectors expose file content and search, but not the comment threads — the review discussion, the anchored quotes, the resolve/reopen history. This server fills that gap for any MCP client (Claude Code, Claude Desktop, Cursor, Cline, etc.), and also works as a plain CLI.

Features

• 2 MCP tools — drive_search_files, drive_get_comments. That's the whole API.
• Reads full comment threads — author, content, the anchored quoted text, resolved/open status, and every reply (with resolve/reopen actions).
• Works across Docs, Sheets, and Slides — the Drive comments API is uniform across file types.
• Accepts URLs or IDs — paste a docs.google.com/document/d/… link or a bare file ID.
• Read-only OAuth scope (drive.readonly).
• Env-var-driven config — DRIVE_MCP_CREDENTIALS, DRIVE_MCP_TOKEN, DRIVE_MCP_SCOPES.

Install

pip install google-drive-comments-mcp
# or, with uv:
uv tool install google-drive-comments-mcp

One-time setup (~10 minutes)

You need a Google Cloud OAuth client. The server runs entirely on your machine; nothing leaves it.

1. Sign in to Google Cloud Console with the account whose Drive comments you want to read.
2. Create a project (or pick an existing one).
3. Enable the Drive API: console.cloud.google.com/apis/library/drive.googleapis.com.
4. Configure the OAuth consent screen under APIs & Services → OAuth consent screen:
   • Google Workspace users: User type = Internal. No app verification is needed even though drive.readonly is a restricted scope.
   • Personal Gmail users: User type = External, and add your own address under "Test users".
5. APIs & Services → Credentials → + Create credentials → OAuth client ID
   • Application type: Desktop app
   • Download the JSON.
6. Run setup:

google-drive-comments-mcp setup --import-credentials ~/Downloads/client_secret_*.json

A browser window opens for OAuth consent. The refresh token is cached at ~/.config/google-drive-comments-mcp/token.json.

Verify:

google-drive-comments-mcp status
google-drive-comments-mcp comments "https://docs.google.com/document/d/YOUR_DOC_ID/edit"

Use it from Claude Code

claude mcp add --scope user google-drive-comments google-drive-comments-mcp -- serve

Then:

Read the open comments on this doc and summarize what reviewers are asking for: https://docs.google.com/document/d/…

Use it from Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac):

{
  "mcpServers": {
    "google-drive-comments": {
      "command": "google-drive-comments-mcp",
      "args": ["serve"]
    }
  }
}

(Use the absolute path from which google-drive-comments-mcp if it isn't on Claude Desktop's $PATH.)

Use it from the shell

# Find a doc
google-drive-comments-mcp search "Q3 strategy"

# Read all comments (open + resolved) on a doc by URL or ID
google-drive-comments-mcp comments "https://docs.google.com/document/d/abc123/edit"

# Only unresolved comments
google-drive-comments-mcp comments abc123 --open-only

The 2 MCP tools

drive_search_files(query, max_results=10)

Search Drive. Plain strings are auto-wrapped as a filename search; raw Drive query syntax passes through.

[
  {
    "id": "1AbC…",
    "name": "Q3 Strategy",
    "mime_type": "application/vnd.google-apps.document",
    "modified": "2026-04-20T09:00:00.000Z",
    "owners": ["Jane Doe"],
    "web_view_link": "https://docs.g

... [View full README on GitHub](https://github.com/zayansalman/google-drive-comments-mcp#readme)