> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tembo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Docs

> Read and update Google Docs documents through MCP.

Read and update Google Docs documents through Google's remote MCP server.

## Prerequisites

You need access to your Tembo organization and a Google Cloud project where you can create OAuth clients. Google's Workspace MCP servers are in Google's Developer Preview, and they don't support dynamic client registration, so each organization connects with its own OAuth client.

## Installation

1. In Google Cloud, enable the Google Docs API and the `docsmcp.googleapis.com` MCP service. See Google's [MCP server setup guide](https://developers.google.com/workspace/guides/configure-mcp-servers).
2. Configure the OAuth consent screen and create a **Web application** OAuth client.
3. Open **Settings → Integrations** in Tembo, find **Google Docs** in the **Productivity** group, and click **Install**. The connection dialog opens with the server URL filled in and **Pre-registered** OAuth selected.
4. Copy the callback URL shown in the dialog and add it as an authorized redirect URI on your Google OAuth client.
5. Enter the **Client ID** and **Client Secret**, then save and authorize with the Google account you want to connect.

The catalog server endpoint is `https://docsmcp.googleapis.com/mcp/v1`.

If you leave **Scope** blank, Tembo requests the scopes the server advertises. Enter a space-separated scope to narrow access. See the [MCP authentication instructions](https://docs.tembo.io/integrations/mcp.md#advanced) for details on pre-registered OAuth clients.

## Usage and verification

Start a new session and ask Tembo to read one of your Google Docs documents. Confirm the tools are available and that any returned data belongs to the Google account you intended to connect.

## Access and troubleshooting

A shared connection uses the Google account of whoever authorized it. Workspace admins can check **Personal MCP** to keep the connection to their own sessions; connections created by non-admins are always personal. Confirm the document before allowing Tembo to update it.

If the connection remains pending, return to **Settings → Integrations** and finish authorization. If tools do not appear, confirm the connection was saved and start a new session. See [MCP troubleshooting](https://docs.tembo.io/integrations/mcp.md#advanced) for authentication and connectivity checks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.