Google Docs MCP server with full tab support, markdown extraction, and batch updates.
A Model Context Protocol server for Google Docs with full tab support — something most existing servers get wrong or skip entirely. Uses Google service accounts with domain-wide delegation, so it works in Workspace orgs without OAuth consent screens. ------|-------------| | List all tabs (including nested) in a document | | Read one tab or all tabs as markdown with proper heading levels | |…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A Model Context Protocol server for Google Docs with full tab support — something most existing servers get wrong or skip entirely. Uses Google service accounts with domain-wide delegation, so it works in Workspace orgs without OAuth consent screens. ------|-------------| | List all tabs (including nested) in a document | | Read one tab or all tabs as markdown with proper heading levels | | Lightweight metadata: title, ID, link, tab list | | Create a new doc with optional initial text | |…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.