MCP server for Google Docs
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"jag-k-google-docs-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Google Docs MCP MCP server for Google Docs. ## Features - Tools: - `docs.read` — Read a Doc as Markdown or HTML - `comments.list` — List comments and replies - `comments.reply` — Reply to a comment (write gated) - `comments.resolve` — Resolve a comment (write gated) - `docs.insert_text` — Insert or append text (write gated) - `docs.from_url` — Normalize a Docs/Drive URL to IDs - `drive.export_file` — Export as PDF/DOCX/HTML - Resources: - `mcp://token-info` — Safe token diagnostics (no secrets) - `gdoc-md://{document_id}` — Google Doc (Markdown) - `gdoc-html://{document_id}` — Google Doc (HTML) - Prompts: - `comment_reply`, `summarize_doc` ## Quick Start - Using CLI (recommended): - Authorize: `uvx google-docs-mcp auth authorize [-f|--force]` - Start server (default stdio): `uvx google-docs-mcp server [--transport stdio|http|sse|streamable-http]` - Using local instance: - Authorize: `uv run google_docs_mcp auth authorize` - Start server: `uv run google_docs_mcp server` ## MCP Config (example) Add to your MCP client configuration (installed CLI): ```toml [mcp_servers.google_docs_mcp] command = "uvx" args = ["google-docs-mcp", "server"] env = { WRITE_MODE = "disabled", GOOGLE__CLIENT_ID = "<id>", GOOGLE__CLIENT_SECRET = "<secret>", } ``` ## OAuth Setup 1) Create OAuth Desktop client in Google Cloud Console. 2) Provide `GOOGLE__CLIENT_ID` and `GOOGLE__CLIENT_SECRET` as env vars, or put a client file in the config dir and set `GOOGLE__OAUTH_CLIENT_FILE`. 3) Run `google-docs-mcp auth authorize` (or `uv run -m google_docs_mcp.cli auth authorize`) and approve scopes. ## Write Safety - Controlled via `WRITE_MODE` env var. Default is `enabled`. Set `disabled` to block any write tools. ## Configuration - This repo provides an auto-generated `Configuration.md` and a starter `.env.example`. They are the source of truth for all env vars and defaults. - Common variables: - `WRITE_MODE`: `enabled` (default) or `disabled` - `…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.