# Google Docs MCP server
The Google Docs MCP server enables AI assistants to create, read, update, and collaborate on Google Docs in a reliable, permission-respecting manner through natural conversation. It allows you to author content, apply edits, propose suggestions, manage comments, surface mentions, and understand recent changes without requiring direct interaction with the Google Docs interface.
# Uses
Use the Google Docs MCP server when you plan to perform the following actions:
- Create new Google Docs with specified titles and initial content
- Read and review document content for summarization or analysis
- Update and revise specific sections of existing documents
- Find specific blocks or sections within documents
- Add, list, and reply to comments for feedback and collaboration
- Manage suggested edits and track pending changes
- Identify and review mentions within documents
- Resolve comment threads when feedback is addressed
# Example prompts
Create a new Google Doc called 'Q4 Product Roadmap' with an outline.Read the quarterly report document and summarize the key findings.Update the executive summary section in the proposal document.Find the paragraph that mentions revenue projections.Add a comment to the budget section asking about the timeline.Show me all the comments on the project plan document.Reply to Jade's comment about the deadline.Who is mentioned in the marketing strategy document?
# Google Docs MCP server tools
The Google Docs MCP server provides the following tools:
| Tool | Description |
|---|---|
| create_document | Creates a new Google Doc under your identity with the title and optional initial content you specify. |
| get_document_info | Retrieves metadata about a Google Doc needed for tab selection and safe write operations. |
| get_document_content | Retrieves the content of a Google Doc. |
| find_blocks | Identifies content blocks within a Google Doc that match the text or structural criteria you provide. |
| update_document_content | Updates an existing Google Doc. |
| list_suggestions | Retrieves suggested edits in a Google Doc with structured context. |
| add_comment | Adds a new comment to a Google Doc. |
| list_comments | Retrieves comment threads for a Google Doc. |
| reply_to_comment | Adds a reply to an existing comment thread in a Google Doc. |
| resolve_comment | Resolves an existing comment thread in a Google Doc. |
| list_mentions | Retrieves mentions in a Google Doc with context about who or what is mentioned and where. |
# Install the Google Docs MCP server
Complete the following steps to install a prebuilt MCP server to your project:
Sign in to your Workato account.
Go to AI Hub > MCP servers.
Click + Create MCP server.
Go to the Start with a template section and select the prebuilt MCP server you plan to use.
Click Use this template.
Provide a name for your MCP server in the MCP server name field.
Go to the Connections section and connect to your app account.
Select the connection type you plan to use for the MCP server template.
- User's connection: MCP server tools perform actions based on the identity and permissions of the user who connects to the application. Users authenticate with their own credentials to execute the skill.
- Your connection: This option uses the connection established by the recipe builder and follows the same principles as normal app connections.
Select your connection type
VERIFIED USER ACCESS AUTHENTICATION REQUIREMENTS
Only app connections that use OAuth 2.0 authorization code grant are available for user's connection. Refer to Verified user access for more information.
Complete the app-specific connection setup steps in the following section.
# Google Docs connection setup
You must complete the following prerequisite setup to establish a Google Docs connection:
- Enable the Google Docs API
- Create a service account
- Generate a service account key
- Share Google Docs with the service account
- Configure OAuth 2.0 for authorization
Proceed to connect to Google Docs on Workato after you complete these prerequisites.
# Enable the Google Docs API
Complete the following steps to enable the Google Docs API:
Sign in to your Google Cloud Console (opens new window).
Go to APIs & Services > Library.
Search for Google Docs API.
Click Enable to activate the API for your project.
# Create a service account
Complete the following steps to create a service account:
Go to IAM & Admin > Service Accounts in the Google Cloud Console.
Click Create Service Account.
Enter a name, ID, and description for the service account.
Click Create and continue.
Assign the required roles such as Editor or Owner, based on permissions required.
Click Done.
# Generate a service account key
Complete the following steps to generate a service account key:
Go to IAM & Admin > Service Accounts and select the newly created service account.
Go to the Keys tab.
Click Add key > Create new key.
Choose JSON as the format and click Create.
Download the JSON key file and store it securely.
# Share Google Docs with the service account
Complete the following steps to share a Google Doc with the service account:
Open Google Docs and select the document you plan to integrate.
Click Share and enter the service account email.
Assign the appropriate permissions.
Click Send.
# Configure OAuth 2.0 for authorization
Complete the following setup in the Google Cloud Console to authorize Google Docs for Workato:
# Configure the OAuth consent screen
Complete the following steps to configure the OAuth consent screen:
Open Google Cloud Console and go to APIs & Services > OAuth consent screen.
Click Get started.
Enter Workato in the App name field.
Enter an email in the User support email field.
Click Next.
Select External as the Audience. Learn more about user types (opens new window).
Click Next.
Enter an email address in the Contact information section.
Select the checkbox to agree to Google API Services User Data Policy (opens new window) and click Continue.
Click Create.
Click the Data access tab and select Add or Remove Scopes.
Select the necessary scopes, such as:
https://www.googleapis.com/auth/documentshttps://www.googleapis.com/auth/documents.readonly
Click Save.
# Authorize the service account
Complete the following steps to authorize the service account:
Go to Security > Access and data control > API Controls.
Go to Domain-wide Delegation and click Manage Domain Wide Delegation.
Click Add new.
Enter the Client ID from the service account JSON file.
Add the necessary scopes from the previous step.
Click Authorize.
# Set up your Google Docs connection
The Google Docs connector supports the following authentication methods:
# Service account
Complete the following steps to set up your connection with a service account:
Click Create > Connection.
Search for and select Google Docs as your connection on the New connection page.
Provide a name for your connection in the Connection name field.
Service account connection
Use the Location drop-down menu to select the project where you plan to store the connection.
Enter your service account email address in the Service account email field.
Enter your private key from the downloaded JSON in the Private key field.
Click Sign in with Google.
# OAuth 2.0
Complete the following steps to set up your connection with OAuth 2.0 authentication:
Click Create > Connection.
Search for and select Google Docs as your connection on the New connection page.
Provide a name for your connection in the Connection name field.
OAuth 2.0 connection
Use the Location drop-down menu to select the project where you plan to store the connection.
Enter your application's client ID in the Client ID field.
You can find your client ID by signing in to your Google Developers Console (opens new window) account. After signing in, click Credentials to show your OAuth 2.0 client IDs. Alternatively, you can create OAuth 2.0 credentials by selecting Create credentials > OAuth client ID. Use https://www.workato.com/oauth/callback as the redirect URI when registering your OAuth client. Learn more (opens new window).
Provide the client secret in the Client secret field. Use the same instructions as the client ID to retrieve the client secret.
Click Sign in with Google.
# How to use Google Docs MCP server tools
Refer to the following sections for detailed information on available tools:
# create_document tool
The create_document tool creates a new Google Doc under your identity with the title and optional initial content you provide. Your LLM uses this tool to create a new Google Doc or turn a discussion, notes, or outline into a document. Try asking:
Create a new Google Doc called 'Q4 Product Roadmap' with section headers for Goals, Timeline, and Resources.Turn our meeting notes into a new document titled 'Project Kickoff Meeting'.Make a new Google Doc for the customer proposal with an executive summary section.Create a document called 'Team OKRs' with an outline structure.
# get_document_info tool
The get_document_info tool retrieves metadata about a Google Doc needed for tab selection and safe write operations, without returning document content blocks. Your LLM uses this tool to refer to a specific tab, obtain the current revision ID before attempting a write operation, or understand document structure.
Try asking:
Get the metadata for the quarterly report document.What tabs exist in the project plan Google Doc?Show me the document info for the Appendix tab.Check the revision ID for the proposal before I update it.
# get_document_content tool
The get_document_content tool retrieves the content of a Google Doc. Your LLM uses this tool to read, review, or use a document as input for downstream tasks such as rewriting, summarization, or quality checks.
Try asking:
Read the quarterly report and summarize the key findings.Show me the contents of the project requirements document.Review the customer proposal and identify any gaps.Extract the action items from the meeting notes document.
# find_blocks tool
The find_blocks tool identifies content blocks within a Google Doc that match the text or structural criteria you provide. Your LLM uses this tool to locate specific sections before applying edits, refer to content by description, or find sections by matching text.
Try asking:
Find the paragraph that starts with 'Our revenue projections'.Locate the Executive Summary section in the proposal.Find all headings that mention 'Timeline' in the project plan.Identify the block containing the budget breakdown.
# update_document_content tool
The update_document_content tool updates an existing Google Doc. Your LLM uses this tool to revise, polish, or update an existing document, including structural changes such as inserting sections or changing heading levels.
Try asking:
Update the executive summary to include the new revenue figures.Change the Timeline section heading to 'Project Timeline and Milestones'.Insert a new paragraph after the introduction explaining the methodology.Revise the conclusion to emphasize the next steps.
# list_suggestions tool
The list_suggestions tool retrieves suggested edits in a Google Doc with sufficient context to understand what suggestions are pending. Your LLM uses this tool to identify suggested edits that are still pending, review suggested changes before applying direct edits, or understand who suggested what and where.
Try asking:
Show me the suggestions on the quarterly report.What edits have been suggested in the project plan?List all pending suggestions in this document.Who suggested changes to the executive summary?
# add_comment tool
The add_comment tool adds a new comment to a Google Doc. Your LLM uses this tool to leave feedback, ask a question, or add commentary in a document without proposing a specific content change.
Try asking:
Add a comment to the budget section asking about the contingency allocation.Leave feedback on the timeline requesting clarification on Phase 2.Comment on the executive summary suggesting we add customer testimonials.Ask a question in the methodology section about the data sources.
# list_comments tool
The list_comments tool retrieves comment threads for a Google Doc with sufficient context to allow follow-on actions such as replying or resolving. Your LLM uses this tool to identify open feedback to address, find a comment thread to reply to, or see what comments are still outstanding.
Try asking:
Show me all the comments on the project plan.What feedback is still open on the quarterly report?List the comment threads that need responses.What comments are outstanding on this document?
# reply_to_comment tool
The reply_to_comment tool adds a reply to an existing comment thread in a Google Doc. Your LLM uses this tool to respond within an existing comment thread.
Try asking:
Reply to Josh's comment about the timeline with an updated deadline.Respond to the feedback on the budget section.Answer Erin's question about the methodology.Reply to the comment asking for more details on Phase 2.
# resolve_comment tool
The resolve_comment tool resolves an existing comment thread in a Google Doc, marking it as addressed. Your LLM uses this tool to mark feedback as addressed or close completed comment threads.
Try asking:
Resolve the comment about the budget now that it's updated.Mark Sarah's feedback as addressed.Close the comment thread about the timeline.Resolve all comments related to the executive summary.
# list_mentions tool
The list_mentions tool retrieves mentions in a Google Doc with context about who or what is mentioned and where. Your LLM uses this tool to find who is mentioned in the document, identify where someone is referenced, or understand who is tagged in specific sections.
Try asking:
Who is mentioned in the project plan document?Where is Sarah referenced in the quarterly report?Show me all mentions of the engineering team.Find where Jordan is tagged in this document.
# Getting started
View and manage your MCP server tools in the Overview page Tools section. Tool management provides the following capabilities:
TOOLS MUST BE STARTED
Your LLM can only access active tools in your MCP server connector.
Last updated: 2/18/2026, 7:01:34 PM