Skip to main content
This guide shows you how to configure the Google Docs connector for WRITER Agent. After setting up this connector, WRITER Agent can perform operations like retrieving document content, searching within documents, editing paragraphs and sections, and inserting new content while maintaining formatting.

​
Set up the Google Docs connector

Configure the Google Docs connector in AI Studio under Connectors & Tools. The Google Docs connector requires organization-managed OAuth authentication.
The Google Docs connector only supports organization-managed OAuth. You must create your own Google Docs OAuth application. Writer-managed OAuth is not available for Google Docs.
Google OAuth credentials expire after 6 months of inactivity. If the Google Docs connector is not used for 6 months, users will need to re-authenticate.

​
Create a Google OAuth application

Create a new Google OAuth application in the Google Cloud Console:
  1. Navigate to the Google Cloud Console
  2. Create a new project or select an existing project
  3. Enable the Google Docs API for your project
  4. Configure the OAuth consent screen with your application details
  5. Create OAuth 2.0 credentials (Web application type)
  6. Add the Writer redirect URI to authorized redirect URIs: 
    https://app.writer.com/mcp/oauth/callback
  7. Configure the required OAuth scopes for your application
  8. Copy the client ID and client secret for use in AI Studio
For detailed instructions, see Google’s OAuth 2.0 documentation.

​
Required OAuth scopes

  • https://www.googleapis.com/auth/documents - Read and write access to Google Docs

​
Configure the connector in AI Studio

  1. Navigate to Connectors & Tools in AI Studio
  2. Select the Google Docs connector
  3. Select who has access by default (all users or specific teams)
  4. Select the connection type:
    • Level: User level (each user authenticates their own account) or org level (shared connection to a single account)
  5. Select which tools to enable for your agents
  6. Enter your OAuth client ID and client secret
  7. Complete the OAuth authorization flow

​
Next steps