MCP server
Google Docs
Let an AI client read and edit controlled Google Docs without granting access to a wider document archive.
Published by the company that makes the product.
What it can access
OAuth inherits the connected user's document access and can permit writes.
Security note
Developer Preview. Give access only to a disposable workshop folder and require a person to review every edit before sharing.
Do you need it?
Use it only for a repeated drafting workflow in Docs. For a single public document, manual upload and paste-back is easier to inspect.
Capability and permissions
Google OAuth can let the client read document content and write changes. Effective access follows the connected user and may be broader than the one document in view.
Least-privilege setup
As of 2026-09-01, the Google Workspace MCP service is Developer Preview. Follow Google’s current guide, use a workshop account, and share only a copied public document. Keep original and approved versions outside the connected account.
Harmless success test
Create a document containing three invented sentences. Ask the client to add a clearly labelled fourth sentence. Inspect version history and confirm no other document changed.
Disable, revoke, remove
Disconnect in the AI client, revoke its Google Account access, remove the workshop account from the document, and delete the test copy.
When not to connect
Do not connect if the account can open legal drafts, witness statements, board minutes, or documents with mixed sharing permissions.