Log inSubmit server
Google Docs MCP logo

Google Docs MCP

Read, edit, format, comment on, and export Google Docs through 27 MCP tools and conversational OAuth setup.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Google Docs MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "google-docs-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@a1-x-tech/mcp-google-docs@latest"
      ],
      "env": {
        "GOOGLE_DOCS_CLIENT_ID": "YOUR_VALUE_HERE",
        "GOOGLE_DOCS_CLIENT_SECRET": "YOUR_VALUE_HERE",
        "GOOGLE_DOCS_REFRESH_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 27 tools correctly (8d ago).

Overview

Google Docs MCP MCP server connects AI applications to the Google Docs API for reading, editing, formatting, commenting on, and exporting documents. It uses exact UTF-16 index ranges for targeted changes and guides assistants to refresh indexes before edits. OAuth begins from the conversation with “connect Google Docs,” using a local PKCE redirect and storing tokens internally. Reach for it when an agent needs controlled document changes, Markdown conversion, comment-thread work, or exports without exposing general-purpose Google Drive tools.

Use cases

  • Read and summarize document content and comment threads
  • Replace exact passages without changing surrounding content
  • Create documents from Markdown
  • Format headings, lists, tables, breaks, and images
  • Export Google Docs to Markdown, PDF, or DOCX

Key features

  • Read documents as text, structure, or Markdown
  • Edit exact UTF-16 index ranges
  • Format text, paragraphs, lists, and tables
  • Manage document comment threads
  • Export to Markdown, PDF, DOCX, and other formats
  • Conversational OAuth with PKCE

Tools27

What Google Docs MCP lets your agent do. Expand a tool for its parameters.

Verified live~8.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 66d

What it can do

From the 27 tools this server returned when we ran it; 27 declare their own safety hints.

Can delete or modify data · 14Handles credentials · 8Makes network requests · 27Read-only tools · 13
Network at startup4 connections
Files written at startup1
Install scriptsprepare
npm provenanceNot published
Package age66 days
Maintainers1

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @a1-x-tech/mcp-google-docs@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.1kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed27Callable tools this server registers over MCP.

How Google Docs MCP works

What Google Docs MCP does

Google Docs MCP gives an AI client tools for working with Google Docs through the Google Docs API. It can read documents as text, structure, or Markdown; create documents from Markdown; modify selected ranges; apply text and paragraph formatting; manage lists, tables, breaks, and inline images; work with comment threads; and export documents to formats including Markdown, PDF, and DOCX.

The server is suited to conversational document workflows where an assistant needs to inspect content before making a narrowly scoped change. Typical requests include rewriting a named paragraph, changing heading levels, inserting a table, summarizing unresolved comments, or exporting a document for delivery.

How it works

Document edits use UTF-16 index positions within a tab body. Insertions and deletions move later positions, so the server directs the assistant to read the document again before each edit and to process edits from the end toward the beginning when appropriate. This approach supports exact range replacement instead of approximate text matching.

Reading a document, its tabs, or its comments does not change Google Docs. Creating a document, inserting or removing content, changing formatting, and managing comments do modify the document. Exporting can write a local file when an output path is supplied while leaving the Google document unchanged.

Markdown conversion works in both directions. A document can be created from Markdown, or its content can be exported as Markdown. Replacing an existing document body with Markdown is an explicitly destructive operation because it replaces the entire body.

Setup and configuration

Node.js 20 or newer and a Google account are required. Installation does not require credentials at install time. After adding the server to an MCP client, say “connect Google Docs” to start the OAuth flow. The server guides the user through creating an OAuth client, handles Google’s redirect on 127.0.0.1 with PKCE, and retains the tokens itself.

The package can be launched with:

Terminal
npx -y @a1-x-tech/mcp-google-docs@latest

The documented setup supports Codex, Claude Code, Claude Desktop, Cursor, and VS Code using a local stdio configuration. Codex can also add it with codex mcp add, while Claude Code uses claude mcp add --transport stdio.

Tools and capabilities

The server provides 27 tools covering:

  • Reading document text, structure, tabs, and Markdown
  • Creating documents and inserting or replacing exact ranges
  • Styling characters and paragraphs, including headings and lists
  • Creating and filling tables
  • Adding page breaks and images from public URLs
  • Listing, replying to, resolving, and adding document-level comment threads
  • Exporting to Markdown, PDF, DOCX, and other supported formats

Images are fetched by Google from a public URL. Supported image types include PNG, JPEG, and GIF.

Limitations and notes

Tabs can be read and targeted, but the API cannot create, rename, delete, or reorder them. New comments cannot be anchored directly to a text range; they attach at the document level and can optionally quote the relevant text.

Importing Markdown replaces the entire document body. Comment anchors, positioned objects, headers and footers, and additional tabs do not survive that conversion. Export files are limited to 10 MB and exclude comments and suggestions. Inline images require a public URL, support PNG, JPEG, or GIF, and are limited to 50 MB and 25 megapixels. The server does not provide a general-purpose Google Drive tool or an upload channel for image files.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Google Docs MCP

Google Docs MCP is an MCP server that connects AI applications to the Google Docs API. Its main tools read documents, edit exact ranges, format text and structure, manage comment threads, create documents from Markdown, and export content to Markdown, PDF, DOCX, and other formats.

Install it as a stdio MCP server with `npx -y @a1-x-tech/mcp-google-docs@latest`. Add that command to Codex, Claude Code, Claude Desktop, Cursor, or VS Code, then connect your Google account from the conversation.

Yes, Google Docs MCP works with Cursor through a stdio entry in `~/.cursor/mcp.json` on macOS and Linux or `%USERPROFILE%\.cursor\mcp.json` on Windows. The configuration uses `npx` with the package’s `@latest` tag.

It authenticates through an OAuth flow started by saying “connect Google Docs.” The server guides OAuth client setup, handles Google’s local `127.0.0.1` redirect with PKCE, and keeps the resulting tokens itself.

No, document exports do not include comments or suggestions. Comment threads can be read and managed through the server separately, while exports support formats including Markdown, PDF, and DOCX.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGoogle Docs MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/google-docs-mcp?style=directory)](https://allmcps.com/mcp/google-docs-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/google-docs-mcp"><img src="https://allmcps.com/api/badge/google-docs-mcp?style=directory" alt="Google Docs MCP on AllMCPs" /></a>