Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
chrischall avatar

Gogcli Mcp Docs

  • 1 repo stars
  • Updated July 27, 2026
  • chrischall/gogcli-mcp

gogcli-mcp-docs is a MCP server that gives Claude extended Google Docs and comment access through gogcli.

About

gogcli-mcp-docs connects coding agents to Google Docs through gogcli, emphasizing auth plus richer Docs and comment operations than a minimal read-only wrapper. Developers often keep PRDs, decision logs, and support macros in Docs while code lives in Git; this MCP server lets Claude Code or Cursor read and update those files when you ask in chat, which speeds spec-driven builds and reduces copy-paste between editor and browser. You install the published npm module, point your host at the stdio server, and rely on the same gogcli login you use for other Google tools in the suite. It does not replace a static docs site generator—it shines when Docs remains your team’s source of truth during build. Expect intermediate setup: binary discovery, OAuth via gogcli, and sharing permissions on each document still matter.

  • stdio MCP server gogcli-mcp-docs v2.6.1 with extended Google Docs and comments support
  • Authentication aligned with gogcli via GOG_ACCOUNT and optional GOG_PATH
  • Full Docs workflows for Claude without hand-rolling Google Docs API calls in your repo
  • Monorepo sibling to Drive, Sheets, and Classroom gogcli MCP packages
  • npm-published package with MCP 2025-12-11 server schema metadata

Gogcli Mcp Docs by the numbers

  • Data as of Jul 28, 2026 (Skillselion catalog sync)
terminal
claude mcp add --env GOG_ACCOUNT=YOUR_GOG_ACCOUNT --env GOG_PATH=YOUR_GOG_PATH gogcli-mcp-docs -- npx -y gogcli-mcp-docs

Add your badge

Show developers this MCP server is listed on Skillselion. Paste this into your README.

Listed on Skillselion
repo stars1
Packagegogcli-mcp-docs
TransportSTDIO
AuthNone
Last updatedJuly 27, 2026
Repositorychrischall/gogcli-mcp

What it does

Draft, edit, and comment on Google Docs from your agent while you ship specs, runbooks, and customer-facing copy.

Who is it for?

Best when you document in Google Docs and want one MCP bridge for edits and comment threads during implementation.

Skip if: Projects that publish docs only as Markdown in-repo with no Google Docs workflow.

What you get

Once registered, the agent can work with Google Docs content and comments using your gogcli-authenticated account from the MCP host.

  • MCP tools for Google Docs operations routed through gogcli
  • Comment-aware Docs workflows callable from the agent
  • Consistent Google auth with other gogcli-mcp packages

By the numbers

  • Version 2.6.1, transport stdio, registry npm identifier gogcli-mcp-docs
  • Environment variables documented: GOG_ACCOUNT, GOG_PATH
  • Repository subfolder packages/gogcli-mcp-docs under github.com/chrischall/gogcli-mcp
README.md

gogcli-mcp

CI npm coverage: 100% license

A monorepo of Model Context Protocol servers that give Claude natural-language access to Google Workspace via gogcli.

[!WARNING] AI-developed project. This codebase was built and is actively maintained by Claude. Review all code and tool permissions before use.

Packages

Package Tools Description
gogcli-mcp 52 All services — Sheets, Docs, Gmail, Calendar, Drive, Tasks, Contacts, Auth
gogcli-mcp-sheets 35 Auth + full Sheets (base + 22 extra: tabs, formatting, named ranges, etc.)
gogcli-mcp-docs 26 Auth + full Docs (base + 14 extra: insert, export, sed, comments, etc.)

Each package is a standalone MCP server. Install whichever one fits your needs — you don't need to install more than one.

Prerequisites

Acknowledgement of Terms

By using this MCP server, you acknowledge and agree to the following:

1. This server accesses your own Google Workspace data via Google's official APIs (Gmail, Calendar, Drive, Sheets, Docs, Contacts). Auth happens via OAuth, with your explicit consent at each scope. It does not — and cannot — access anyone else's Google account or shared content you don't have permission to read.

2. Google's APIs Terms of Service govern your use of this server, in addition to any Google Workspace Acceptable Use Policy your domain admin enforces. The clauses most relevant here:

Google sets and enforces limits on your use of the APIs (e.g. limiting the number of API requests that you may make or the number of users you may serve), in our sole discretion.

And on credentials, which is the most-tripped-on clause for open-source projects:

You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open source projects.

You are agreeing to those terms — read by the maintainer 2026-05-23 — every time you invoke a tool in this server.

3. You must configure your own OAuth client. This MCP does not ship an embedded client_secret.json. You register your own OAuth client at https://console.cloud.google.com/, scope it to your own user/project, and authorize it for the Workspace APIs you want to use. Do not check client_secret.json, credentials.json, or any refresh tokens into git — these are credentials and Google's ToS explicitly prohibits embedding them in OSS.

4. Personal, single-user use only. This project is not affiliated with, endorsed by, sponsored by, or in partnership with Google LLC. It is a personal automation tool for one Google account holder to read and write their own Workspace content. Do not use it to bulk-extract Workspace data from your org, automate against other users' accounts, or build a multi-tenant SaaS on top of it. If you want to do those things, you need a verified app, a domain-wide-delegation service account, and a Workspace admin's blessing — none of which this MCP provides.

5. Your domain admin's policy may add restrictions. If you're using a corporate Google Workspace account, your admin may restrict third-party OAuth apps, prohibit data exfiltration, or require app verification. Check with your IT admin before authorizing this MCP against a corporate domain.

6. You accept full responsibility for any consequences of using this server in connection with your Google account — quota exhaustion (Gmail and Drive APIs have aggressive per-user quotas), token revocation, account warnings, your domain admin emailing you, or any enforcement action. If Google or your domain admin objects to your use, stop using this server.

This section is the maintainer's good-faith summary of the terms — it is not legal advice and does not modify or supersede Google's actual APIs ToS or your domain's policies.

Install gogcli

gogcli is the CLI that these MCP servers wrap. Install it for your platform:

macOS (Homebrew):

brew install steipete/tap/gogcli

macOS / Linux (binary):

curl -fsSL https://github.com/openclaw/gogcli/releases/latest/download/gog-$(uname -s | tr '[:upper:]' '[:lower:]')-$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') -o /usr/local/bin/gog
chmod +x /usr/local/bin/gog

Windows (Scoop):

scoop bucket add steipete https://github.com/steipete/scoop-bucket
scoop install gogcli

Windows (manual):

Download gog-windows-amd64.exe from the latest release, rename to gog.exe, and add to your PATH.

Authenticate

gog auth add your@gmail.com

This opens a browser for Google OAuth. For specific services only:

gog auth add your@gmail.com --services sheets,docs,drive

Install Node.js

Node.js 18 or later is required. Install via nodejs.org or:

brew install node        # macOS

Quick Start

# Install the package you want
npm install -g gogcli-mcp          # base
npm install -g gogcli-mcp-sheets   # extended sheets
npm install -g gogcli-mcp-docs     # extended docs

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "gogcli": {
      "command": "gogcli-mcp",
      "env": {
        "GOG_ACCOUNT": "you@gmail.com"
      }
    }
  }
}

Replace gogcli-mcp with gogcli-mcp-sheets or gogcli-mcp-docs for extended packages.

Claude Code

claude mcp add gogcli -- gogcli-mcp

What you can do

Ask Claude things like:

  • "Read the data in Sheet1!A1:D20 of my budget spreadsheet"
  • "Append this week's expenses to my tracking sheet"
  • "Search my Gmail for invoices from last month"
  • "Create a calendar event for tomorrow at 3pm"
  • "List comments on my project doc"
  • "Export my doc as a PDF"

Multiple Accounts

All tools accept an optional account parameter:

Read Sheet1!A1:D10 from spreadsheet abc123 using my work account work@company.com

Development

npm install        # install all workspace dependencies
npm run build      # build all packages
npm test           # test all packages (267 tests, 100% coverage)
npm run typecheck  # typecheck all packages

Security

  • No credentials are stored or passed by these servers — authentication is handled by gogcli's keyring
  • All gogcli invocations use --no-input to prevent interactive prompts
  • All arguments are passed as arrays to child_process.spawn — no shell injection risk
  • GOG_ACCESS_TOKEN is stripped from the child process environment to prevent stale token auth

License

MIT

Recommended MCP Servers

How it compares

MCP Docs bridge via gogcli, not a static-site or Notion-specific docs skill.

FAQ

Who is gogcli-mcp-docs for?

Developers and founders who keep specs and runbooks in Google Docs and use Claude Code, Cursor, or Codex with MCP.

When should I use gogcli-mcp-docs?

Use it during build when you need the agent to read, update, or discuss Google Docs and comments while implementing features or writing technical documentation.

How do I add gogcli-mcp-docs to my agent?

Add the gogcli-mcp-docs npm package as a stdio MCP server, authenticate with gogcli, set GOG_ACCOUNT, then reference the server in your Claude Code or Cursor MCP settings.

Developer Toolsdocsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.