Gogcli Mcp Docs
Draft, edit, and comment on Google Docs from your agent while you ship specs, runbooks, and customer-facing copy.
Overview
gogcli-mcp-docs is a MCP server for the Build phase that gives Claude extended Google Docs and comment access through gogcli.
What is this MCP server?
- 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
- 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
Community signal: 1 GitHub stars.
What problem does it solve?
Your agent can edit code but cannot touch the Google Doc where your spec and comments actually live.
Who is it for?
Solo builders who 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 do I get? / Deliverables
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
Recommended MCP Servers
Journey fit
Documentation and collaborative writing happen while you build the product; Google Docs is a common sink for PRDs, API notes, and launch copy. Extended Docs and comments support maps directly to the docs subphase where builders maintain living documents agents and humans share.
How it compares
MCP Docs bridge via gogcli, not a static-site or Notion-specific docs skill.
Common Questions / FAQ
Who is gogcli-mcp-docs for?
Developers and solo 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.