Google Drive Comments MCP

Name: Google Drive Comments MCP
Author: zayansalman

by zayansalmanversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.zayansalman/google-drive-comments-mcp

Install

Overview

Description from the maker (original English)

Minimal MCP server for reading comments on Google Drive files (Docs, Sheets, Slides). Read-only.

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
UsageiVery new↓ 27/wk · ★ –

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
You need to fill in: DRIVE_MCP_TOKEN

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: DRIVE_MCP_CREDENTIALS, DRIVE_MCP_TOKEN, DRIVE_MCP_SCOPES

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx 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": {
    "google-drive-comments": {
      "command": "uvx",
      "args": [
        "google-drive-comments-mcp",
        "serve"
      ],
      "env": {
        "DRIVE_MCP_CREDENTIALS": "your-value",
        "DRIVE_MCP_TOKEN": "your-value",
        "DRIVE_MCP_SCOPES": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add google-drive-comments --env DRIVE_MCP_CREDENTIALS=your-value --env DRIVE_MCP_TOKEN=your-value --env DRIVE_MCP_SCOPES=your-value -- uvx google-drive-comments-mcp serve

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": {
    "google-drive-comments": {
      "command": "uvx",
      "args": [
        "google-drive-comments-mcp",
        "serve"
      ],
      "env": {
        "DRIVE_MCP_CREDENTIALS": "your-value",
        "DRIVE_MCP_TOKEN": "your-value",
        "DRIVE_MCP_SCOPES": "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": {
    "google-drive-comments": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "google-drive-comments-mcp",
        "serve"
      ],
      "env": {
        "DRIVE_MCP_CREDENTIALS": "your-value",
        "DRIVE_MCP_TOKEN": "your-value",
        "DRIVE_MCP_SCOPES": "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

DRIVE_MCP_CREDENTIALS env
Path to the Google OAuth client secret JSON. Default: $XDG_CONFIG_HOME/google-drive-comments-mcp/credentials.json.
DRIVE_MCP_TOKEN secret env
Path to the cached Google OAuth refresh token. Default: $XDG_CONFIG_HOME/google-drive-comments-mcp/token.json.
DRIVE_MCP_SCOPES env
Comma-separated Google OAuth scopes. Default: https://www.googleapis.com/auth/drive.readonly.

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 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account zayansalman, 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 3607 servers in this category
Published to the registry more recently than 14% of the other 3607 servers in this category
Basic checks equal to or better than 100% of the other 3607 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 Google Drive 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?

You need to fill in: DRIVE_MCP_TOKEN

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.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) 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:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

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

by BuilderIOWidely used★ 7.6KUpdated 2 months ago

Runs in the cloud

Install

Excel MCP Server

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

by haris-musaWidely used↓ 49.6K/wk★ 4.3KUpdated 8 days ago

Runs on your computer

Install

MCP Server for Excel

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

by sbroenneGrowing↓ 4.3K/wk★ 847Updated 6 days ago

Runs on your computer

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.

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.

Sign in to Google Cloud Console with the account whose Drive comments you want to read.
Create a project (or pick an existing one).
Enable the Drive API: console.cloud.google.com/apis/library/drive.googleapis.com.
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".

APIs & Services → Credentials → + Create credentials → OAuth client ID

Application type: Desktop app
Download the JSON.

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.google.com/document/d/1AbC…/edit" } ]

`drive_get_comments(file, include_resolved=True)`

Read all comments on a file. file accepts a Docs/Sheets/Slides/Drive URL or a bare file ID.

"file": { "id": "1AbC…", "name": "Q3 Strategy", "mime_type": "…document", "web_view_link": "…", "owners": ["Jane Doe"] }, "open_count": 2, "resolved_count": 1, "comments": [ { "id": "AAAA…", "author": "Jane Doe", "content": "Can we add the unit-economics table here?", "quoted_text": "Our margins improved in Q3.", "resolved": false, "created": "2026-04-21T10:00:00Z", "modified": "2026-04-21T10:00:00Z", "replies": [ { "author": "John Smith", "content": "Added.", "action": "", "created": "2026-04-21T11:00:00Z" } ] } ] }

quoted_text is the document text the comment is anchored to — useful context for understanding what each comment refers to.

Configuration

Variable	Default	What
`DRIVE_MCP_CREDENTIALS`	`~/.config/google-drive-comments-mcp/credentials.json`	OAuth client secret JSON
`DRIVE_MCP_TOKEN`	`~/.config/google-drive-comments-mcp/token.json`	Cached refresh token
`DRIVE_MCP_SCOPES`	`https://www.googleapis.com/auth/drive.readonly`	OAuth scopes (comma-separated)
`XDG_CONFIG_HOME`	`~/.config`	Standard XDG override

Sharing one login with other Google MCP tools

If you also run a sibling tool (e.g. gmail-attachments-mcp) and want a single OAuth consent for both, point both tools at the same credential + token files (via the env vars above, or symlinks) and authorize once with the combined scopes:

DRIVE_MCP_SCOPES="https://www.googleapis.com/auth/gmail.readonly,https://www.googleapis.com/auth/drive.readonly" \

google-drive-comments-mcp setup --reauth

A token granted a superset of scopes satisfies each tool's narrower request.

Security

Read-only: the default scope is drive.readonly. It cannot edit, comment, or delete — only read file metadata, content, and comments.
Scope breadth: drive.readonly grants read access to all your Drive files, not just the one you query. There is no per-file read scope that also exposes comments. Treat the cached token like a password (it's written 0600).
No telemetry: your OAuth client lives in your own Google Cloud project. Nothing leaves your machine.

Troubleshooting

`HttpError 403: Google Drive API has not been used in project … before or it is disabled` Enable the Drive API on the project that owns your OAuth client, then retry.

`No valid Google token` from Claude Desktop / cron Run google-drive-comments-mcp setup once in a terminal where a browser can open. Subsequent runs reuse the cached token.

Comments come back empty on a file you know has comments Confirm you authorized the account that can actually see the file, and that the file genuinely has comments (suggestions are not comments). Resolved comments are included unless you pass --open-only / include_resolved=false.

Authentication — bring your own Google OAuth client

There are no API keys and no shipped secrets. The server authenticates to *your* Google account with an OAuth client *you* create, and caches a refresh token locally. The author has zero access to your data.

Why your own client? Google's restricted scopes (here, drive.readonly) can't be redistributed in a shared app, and an unverified shared app is capped at 100 users. "Bring your own OAuth client" is the standard pattern for personal-data MCP servers.
What you need: a free Google Cloud project, the Drive API enabled, an OAuth consent screen, and a Desktop OAuth client. Full walkthrough → docs/setup-google-oauth.md.
Where your token lives: ~/.config/google-drive-comments-mcp/token.json (mode 0600). Delete it to revoke locally; revoke fully at myaccount.google.com/permissions.
No hosted/SaaS option — everything runs locally; your Drive data never touches a third-party server.

More guides

docs/setup-google-oauth.md — full OAuth walkthrough + common errors
docs/claude-code.md · docs/claude-desktop.md · docs/other-clients.md — per-client setup (Cursor, Cline, Continue, …)
examples/ — runnable snippets

Related tools

Part of a small family of focused, local MCP servers for Google Workspace data the hosted connectors don't expose:

[gmail-attachments-mcp](https://github.com/zayansalman/gmail-attachments-mcp) — download Gmail attachment bytes to disk
google-drive-comments-mcp — read comment threads on Docs/Sheets/Slides *(this repo)*
[google-drive-files-mcp](https://github.com/zayansalman/google-drive-files-mcp) — move/organize Drive files

They can share one OAuth login or stay isolated — see each repo's setup.

License

MIT. See LICENSE.

Google Drive 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

google-drive-comments-mcp

Features

Install

or, with uv:

One-time setup (~10 minutes)

Use it from Claude Code

Use it from Claude Desktop

Use it from the shell

Read all comments (open + resolved) on a doc by URL or ID

Only unresolved comments

The 2 MCP tools

drive_search_files(query, max_results=10)

drive_get_comments(file, include_resolved=True)

Configuration

Sharing one login with other Google MCP tools

Security

Troubleshooting

Authentication — bring your own Google OAuth client

More guides

Related tools

License

`drive_search_files(query, max_results=10)`

`drive_get_comments(file, include_resolved=True)`