google-docs-mcp-server-ahmedlaminou

# Google Docs MCP Server <!-- mcp-name: io.github.AhmedLaminou/google-docs-mcp-server --> An open-source, stdio-first MCP server exposing **100 Google Docs and Drive tools**. ## User experience End users do not need their own Google Cloud project. The published package uses this project's public Desktop OAuth client identity. Each user signs into their own Google account and stores a separate token only on their own machine. ```text User prompt → AI client → local stdio MCP server → user's local OAuth token → user's Google Docs ``` The publisher does not receive user tokens or document content in local stdio mode. ## Install and authenticate After publication: ```powershell uvx --from google-docs-mcp-server-ahmedlaminou google-docs-mcp-auth login ``` The browser consent flow stores the token in: - Windows: `%APPDATA%\GoogleDocsMCP\token.json` - macOS: `~/Library/Application Support/GoogleDocsMCP/token.json` - Linux: `~/.config/google-docs-mcp/token.json` Useful commands: ```powershell google-docs-mcp-auth status google-docs-mcp-auth logout ``` Optional reliability settings: ```powershell $env:GOOGLE_DOCS_MCP_HTTP_TIMEOUT = "60" $env:GOOGLE_DOCS_MCP_API_RETRIES = "2" ``` ## MCP client ```json { "mcpServers": { "google-docs": { "command": "uvx", "args": [ "--from", "google-docs-mcp-server-ahmedlaminou", "google-docs-mcp-server" ] } } } ``` The VS Code extension registers this stdio server automatically. ## Permission profiles The public/default profile requests: - `documents` — read and edit Google Docs. - `drive.file` — Drive operations for files created by or explicitly opened with the app. This avoids the restricted full-Drive scope. Broad Drive listing/search and permission operations therefore only see files available to `drive.file`. Self-hosters can intentionally opt into restricted full-Drive access: ```powershell $env:GOOGLE_DOCS_MCP_SCOPE_PROFILE = "full" google-docs-m…