Hosting

Google-managed remote

Transport

Streamable HTTP

Endpoint

https://docsmcp.googleapis.com/mcp/v1

Authentication

OAuth 2.0. Configure the consent screen and an OAuth client marked “Use this client for an AI-powered agent”; grant only the listed product scopes and sign in with the Google account that should be accessible.

Requirements

• Membership in the Google Workspace Developer Preview Program.
• A Google Cloud project, with the relevant Workspace API and its MCP service enabled.
• A supported remote MCP client and a Google account with access to the target Workspace data.
• OAuth 2.0 consent configuration with these scopes: https://www.googleapis.com/auth/drive.readonly, https://www.googleapis.com/auth/drive.file, https://www.googleapis.com/auth/documents.readonly, https://www.googleapis.com/auth/documents.

Setup steps

1. Join the Google Workspace Developer Preview Program and select/create a Google Cloud project.
2. Enable Google Docs API and the matching MCP service in that project.
3. Configure Google Auth Platform consent and add the scopes shown in Requirements.
4. Create an OAuth 2.0 client for an AI agent; use the redirect URI required by your MCP client.
5. Add this server URL to the client: https://docsmcp.googleapis.com/mcp/v1
6. Authenticate with the intended Google account, grant the requested scopes, refresh the tool list, and verify the listed operations.

Two tools read and update Docs. update_doc changes document content. Google preview capabilities can evolve; this is the current listed baseline.

• read_doc

  Officially listed read_doc tool.

  01
• update_doc

  Officially listed update_doc tool.

  02

• Developer Preview

• official source

  Official Google primary MCP reference checked 2026-10-28.

• official source

  Official Google primary MCP reference checked 2026-10-28.

Documentation checked 2026-10-28. Connection has not been runtime tested.