Google Docs MCP

Name: Google Docs MCP
Author: yeyo11

by yeyo11version 0.1.2i★ –iRuns on your computer

Registry nameio.github.yeyo11/google-docs-mcp

Install

Overview

Description from the maker (original English)

Read-only server that explains a Google Doc's comments and reply threads to an AI assistant.

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

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).
The registry lists no key to fill in.

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": {
    "google-docs": {
      "command": "npx",
      "args": [
        "-y",
        "@yeyo11/google-docs-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add google-docs -- npx -y @yeyo11/google-docs-mcp

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "google-docs": {
      "command": "npx",
      "args": [
        "-y",
        "@yeyo11/google-docs-mcp"
      ]
    }
  }
}

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-docs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@yeyo11/google-docs-mcp"
      ]
    }
  }
}

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.

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 yeyo11, 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 Otheri

More stars than 0% of the other 32708 servers in this category
Published to the registry more recently than 97% of the other 32708 servers in this category
Basic checks equal to or better than 100% of the other 32708 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 Docs 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.2) reached the registry yesterday.

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: Spec Driven Development, Remote Desktop Commander, OpenTakeoff

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

OpenTakeoff

by Kentucky-ai

Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.

Runs on your computerUpdated today

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-docs-mcp

A read-only Model Context Protocol server for Google Docs. Its job is to explain a document's comments to an AI assistant (Claude or any MCP client) in full detail: who wrote each one, when, on which piece of text, whether it is open or resolved, the complete reply thread, and who resolved it.

Read-only by design. It only requests the documents.readonly and drive.readonly scopes. There is no tool that creates, edits, resolves or deletes anything, and every tool is advertised with readOnlyHint: true.
OAuth 2.0 sign-in. Users authenticate with their own Google account through the desktop-app flow with PKCE. Tokens are stored locally and refreshed automatically (see the seven-day exception for External apps in Testing mode).
Zero configuration for the assistant. Tools accept a document ID *or* a full Google Docs URL.

Built by José Antonio Garrido. I write about the developer tools I build on my blog, josegarrido.dev.

Tools

Tool	What it does
`list_comments`	The main tool. Every comment in full detail: author, dates, open/resolved status, quoted text, the whole reply thread (including who resolved or reopened it) and, optionally, the paragraph of the document where the quoted text appears. Filter by status, include deleted comments, paginate, and choose `markdown` or `json` output.
`get_comments_summary`	Aggregate view: counts by status, participants and their activity, open comments with no replies, open comments waiting for the original author, oldest open comment and latest activity.
`get_comment`	A single comment thread by ID, with context.
`get_document`	Document metadata plus plain-text content (all tabs), so the assistant can understand what the comments refer to.
`list_documents`	Search Google Docs in Drive (shared drives included) by title or full text.
`get_auth_status`	Whether the server is signed in and with which account.

Example: `list_comments`

# Q4 project plan

Document ID: 1AbC...
Link: https://docs.google.com/document/d/1AbC.../edit
Owner: Ana
Last modified: 2026-09-22 08:00 UTC by Jose (you)

Comments (all): 2

[1] 🟢 OPEN — Ana · 2026-09-22 08:00 UTC

Quoted text (what the comment refers to):

delivery date

Surrounding paragraph (#7):

The delivery date will be shared with the client once the scope is final.

Comment: The delivery date is missing.

_No replies yet._

Comment ID: AAAAxyz

[2] ✅ RESOLVED — Ana · 2026-09-20 10:32 UTC

... Thread (2 replies):

Jose (you) · 2026-09-21 09:00 UTC: Yes, moving it.
Jose (you) · 2026-09-21 12:00 UTC — marked as RESOLVED

Resolved by Jose (you) on 2026-09-21 12:00 UTC.

Comment and reply authors appear by display name: the Drive API doesn't populate their email address. A document's owner and last editor show an email when Google makes it visible to you.

Quick start

Prerequisites

Node.js >= 20
A Google Cloud project with the Google Drive API and Google Docs API enabled

1. Create an OAuth client in Google Cloud

Open the Google Cloud Console and create or select a project.
APIs & Services → Library: enable *Google Drive API* and *Google Docs API*.
APIs & Services → OAuth consent screen: configure it. Use *Internal* for a Workspace organization; for *External* apps in testing mode, add your account as a test user.
APIs & Services → Credentials → Create credentials → OAuth client ID, application type Desktop app.
Download the JSON and save it as ~/.config/google-docs-mcp/credentials.json.

External apps in Testing mode have to sign in again every seven days. With an *External* consent screen whose

publishing status is *Testing*, Google

issues a refresh token that expires in 7 days,

so automatic renewal stops working and tools report that the sign-in expired until you repeat step 2. The running

server picks up the new sign-in without a restart. An *Internal* consent screen (Workspace organizations only) doesn't

have this limit. Neither does publishing the app (*In production*), but drive.readonly is a restricted scope, so

Google then

shows an unverified-app warning and caps the project at 100 users

unless the app is verified.

You can use environment variables instead of the file:

export GOOGLE_CLIENT_ID="...apps.googleusercontent.com"

export GOOGLE_CLIENT_SECRET="..."

2. Sign in with Google

npx -y -p @yeyo11/google-docs-mcp google-docs-mcp-auth

Your browser opens (or the URL is printed so you can paste it). Google asks for read-only access to Drive and Docs. Tokens are saved to ~/.config/google-docs-mcp/token.json with 0600 permissions. Run the same command again to switch accounts.

3. Register the server with your MCP client

No clone or build step is needed; npx fetches the package on first use.

Claude Desktop (claude_desktop_config.json):

"mcpServers": { "google-docs": { "command": "npx", "args": ["-y", "@yeyo11/google-docs-mcp"] } } }

Claude Code:

claude mcp add google-docs -- npx -y @yeyo11/google-docs-mcp

Any other MCP client that supports stdio servers works the same way. If you use environment variables for the OAuth client, add them to the env block of your client configuration.

Running from source instead

git clone https://github.com/yeyo11/google-docs-mcp.git

cd google-docs-mcp npm install npm run build npm run auth

Then point your MCP client at node /absolute/path/to/google-docs-mcp/dist/index.js.

4. Ask away

"Summarize the open comments in https://docs.google.com/document/d/…/edit and tell me which ones are waiting on me."

Configuration

Variable	Description	Default
`GOOGLE_OAUTH_CREDENTIALS`	Path to the OAuth client JSON.	`~/.config/google-docs-mcp/credentials.json`
`GOOGLE_CLIENT_ID` / `GOOGLE_CLIENT_SECRET`	Alternative to the JSON file.	—
`GOOGLE_DOCS_MCP_TOKEN_PATH`	Where the user's tokens are stored.	`~/.config/google-docs-mcp/token.json`
`GOOGLE_DOCS_MCP_CONFIG_DIR`	Base directory for the two files above.	`~/.config/google-docs-mcp`

How it works

MCP client ──stdio──▶ google-docs-mcp ──OAuth2 (read-only)──▶ Google Drive API (files, comments)

└▶ Google Docs API (document text)

Comments come from the Drive API (comments.list / comments.get) with every field requested explicitly, so nothing is silently dropped: quoted text, replies, resolve/reopen actions, deleted flags.
The "surrounding paragraph" is found by locating the quoted text inside the document body fetched from the Docs API (all tabs are traversed, including tables).
Google API errors (401/403/404/429) are returned as MCP isError results with an actionable message instead of breaking the session. Logs go to stderr; stdout is reserved for the protocol.

Development

npm run dev        # run the server from src/ with tsx

npm run typecheck # type-check without emitting npm test # smoke test: tool listing, error handling without credentials, comment formatting

See CONTRIBUTING.md for the workflow and commit conventions.

Security

Only read-only scopes are requested; Google never grants this client write access.
If the stored token lacks the expected scopes, the server refuses to use it and asks you to sign in again.
credentials.json and token.json are git-ignored. Never commit them.
To revoke access, remove the app at https://myaccount.google.com/permissions and delete token.json.

To report a vulnerability, see SECURITY.md.

Limits

Read-only. It can't create, reply to or resolve comments, or edit documents.
Google Docs only. Sheets, Slides and other file types are refused, by URL and by bare ID.
Suggestions, assignments and mentions aren't read as such. A comment is its text, status and thread: an assigned comment looks like any other and a mention is just part of the text. Depending on your access, text pending as a suggestion can appear in get_document as ordinary text.
Comment authors are told apart by display name, since Drive doesn't return their email. In get_comments_summary, two people with the same name count as one.
`get_document` returns plain body text from all tabs, tables included: no formatting, images, smart chips, headers, footers or footnotes. 20,000 characters by default, 500,000 at most (max_chars).
The surrounding paragraph is found by searching for the quoted text. It takes the first match, so a repeated phrase can point to the wrong paragraph, and it may be missed if the text was edited after the comment. Quotes under 8 characters get no paragraph, and paragraphs over 600 characters are trimmed.
`list_comments` pages by 100. Use page_token for the rest. The status filter applies to each page, so a page can come back short or empty while more remain. get_comments_summary reads every page.
One Google account per installation. Run the sign-in command again to switch.
Local stdio only. There is no remote or HTTP transport.
Tokens are stored unencrypted in token.json, with 0600 permissions.
`drive.readonly` covers all of Drive the account can see, not only Docs. The tools read Docs only, but that is what you grant on Google's sign-in screen and what the stored token allows.
What a tool returns reaches the assistant. Document text, comments, names and email addresses go to whichever assistant and model provider you use. Text written by other people arrives as is, so treat it as untrusted.

Roadmap

Optional write tools (reply, resolve) behind an explicit opt-in scope
Multiple accounts / profiles
Streamable HTTP transport for remote deployments

License

MIT

Google Docs MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

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 Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

OpenTakeoff

README from the maker

google-docs-mcp

Tools

Example: list_comments

Comments (all): 2

[1] 🟢 OPEN — Ana · 2026-09-22 08:00 UTC

[2] ✅ RESOLVED — Ana · 2026-09-20 10:32 UTC

Quick start

Prerequisites

1. Create an OAuth client in Google Cloud

2. Sign in with Google

3. Register the server with your MCP client

4. Ask away

Configuration

How it works

Development

Security

Limits

Roadmap

License

Example: `list_comments`