Google Docs
Let agents create and update Google Docs using OAuth2 or service accounts for specs, runbooks, and launch copy.
Overview
com.pulsemcp/google-docs is a MCP server for the Build phase that connects agents to Google Docs via OAuth2 or service account credentials.
What is this MCP server?
- OAuth2 path with client ID, secret, and refresh token from oauth-setup flow
- Optional service account client email and private key for Workspace delegation
- Stdio npm package google-docs-workspace-mcp-server via npx
- Pairs with other PulseMCP Google Workspace servers for unified agent stacks
- Version 0.1.2 on MCP server schema 2025-09-29
- Dual auth: OAuth2 and service account
- Stdio transport via npx
Community signal: 70 GitHub stars.
What problem does it solve?
Product and API documentation locked in Google Docs stays invisible to agents until someone manually pastes excerpts.
Who is it for?
Indie builders who centralize specs and runbooks in Docs and want agent edits during build and ship prep.
Skip if: Teams standardized on Notion or Markdown repos only, or those skipping Google API credential management.
What do I get? / Deliverables
Once credentials are configured, agents read and write Google Docs through MCP instead of manual export loops.
- Google Docs MCP registration in agent config
- Agent-driven read and write access to selected Docs
Recommended MCP Servers
Journey fit
How it compares
Google Docs MCP integration, not a markdown doc generator skill or static site CMS.
Common Questions / FAQ
Who is com.pulsemcp/google-docs for?
Builders using Google Docs for specs who run Claude Code, Cursor, or Codex with MCP integrations.
When should I use com.pulsemcp/google-docs?
When agents must pull or update live Google Doc content during development, docs, or launch writing workflows.
How do I add com.pulsemcp/google-docs to my agent?
Add stdio npx google-docs-workspace-mcp-server to MCP config and set OAuth refresh token or service account env variables.