A1-x-Tech/mcp-google-docs

**English** | Русский
**A1 Google Docs MCP** lets an AI app read and edit Google Docs in plain language. Read a document as text or Markdown, change an exact passage, style headings, lists and tables, work through comment threads and export the result to PDF or DOCX.
It uses the Google Docs API with your Google account. It edits by exact index ranges rather than by guesswork, and makes the limits of the Docs API explicit instead of implying that every document task is possible.
- **27 tools.** Read a document as text, structure or Markdown, edit exact ranges, style characters and paragraphs, manage lists, tables, breaks, images and comment threads, and export to PDF, DOCX and more.
- **Connects from the conversation.** Say "connect Google Docs": the server walks you through the OAuth client, catches Google's redirect on 127.0.0.1 with PKCE and keeps the tokens itself — no config files, no restart.
- **Edits are surgical.** Changes address exact index ranges, and the server steers the assistant to re-read the document before every edit, because each change shifts the indexes after it.
- **Markdown both ways.** Create a document from Markdown or export to Markdown, PDF, DOCX and other formats; replacing a whole document with Markdown is a separate, explicitly destructive step.
- **No hidden Drive surface.** Export, Markdown conversion and comments use Drive endpoints internally, but the server exposes no general-purpose Drive tool.
Start with a read-only question:
> Read the launch plan document and summarize its unresolved comment threads.
Connect the server · Explore use cases · Open technical documentation
---
See it work in a minute
> **You:** Show me the text and comments of the launch plan document.
>
> **Assistant:** Reads the document as compact text blocks and lists its comment threads. Nothing changes.
>
> **You:** Rewrite the “Timeline” paragraph to say the beta starts on March 3.
>
> **Assistant:** Shows the exact range it will replace and the proposed text, then asks for confirmation before editing.
>
> **You:** Confirm.
>
> **Assistant:** Replaces that one range. The rest of the document, its formatting and its comments stay as they were.
Contents
- Quick start
- What you can ask it to do
- How a document changes
- What can change
- Getting access
- Configuration
- Data, limits and background work
- Technical documentation
- Support
Quick start
You need Node.js 20+ and a Google account. Credentials are not required at install time — the server connects from the conversation.
1. Add the server to your AI app.
2. Say "connect Google Docs": the assistant walks you through creating the OAuth client and approving access without editing config files.
3. Ask the read-only question above.
Codex
**In the app:** open **Settings → MCP servers**, select **Add server**, choose **STDIO**, enter the command npx -y @a1-x-tech/mcp-google-docs@latest and environment variables GOOGLE_DOCS_CLIENT_ID, GOOGLE_DOCS_CLIENT_SECRET, GOOGLE_DOCS_REFRESH_TOKEN, then select **Save** and **Restart**.
**From the command line:**
Codex MCP documentation
Claude Code
Claude Code MCP documentation
Claude Desktop
The current official path is **Settings → Extensions**. For a custom desktop extension, open **Advanced settings → Extension Developer → Install Extension…**, select a .mcpb file and follow the prompts.
This repository currently publishes an npm stdio package and does not contain a .mcpb bundle. For Claude Desktop builds that still support local configuration, use the following JSON stdio configuration as a fallback:
In those builds, save it to ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows.
Claude Desktop MCP documentation
Cursor
Add this to ~/.cursor/mcp.json on macOS/Linux or %USERPROFILE%\.cursor\mcp.json on Windows: