Skip to main content

Google Docs MCP server

Automate document creation, editing, and formatting at scale with an AI agent. This MCP server enables programmatic access to create reports from templates, insert data and tables, apply company branding, and manage collaborative workflows—eliminating manual document work.

Setting up an MCP server

This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the Authentication section on this page.

Before you begin

You'll need:

  • Access to AI Gateway with permission to create MCP servers.
  • API credentials for the application you're connecting (see the Authentication section on this page for what to collect).

Create an MCP server

Find the app in the catalog

  1. Sign in to AI Gateway and select App Catalog from the left navigation.
  2. Search for the application you want to connect, then select it from the catalog.
  3. Select Create MCP Server to start the wizard.

App Configuration

Confirm the Base URL for the API, then, under Tools, select the endpoints you want to expose. Select Next.

MCP Server Setup

  1. Enter a Name for your server — something descriptive that identifies both the application and its purpose.
  2. Enter a Description so your team knows what the server is for.
  3. Set the log level: choose Production Mode for terser logs, or Non-Production Mode for more verbose logs that can help with debugging.
  4. Select Next.

Authentication

Enter the authentication details for the application. This varies by service — see the Authentication section on this page for the specific credentials, OAuth URLs, and scopes to use.

Review

Look over the summary of your MCP server configuration, then select Create & Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.


Connect to an AI client

Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:

Tips

  • You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
  • If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.

Authentication

Google Docs API uses OAuth 2.0 for secure access. Set up your project in Google Cloud Console, enable the Google Docs and Google Drive APIs, and create OAuth credentials. In Google Cloud Console, go to APIs & Services > Credentials and create a Web application OAuth 2.0 credential.

ValueSetting
Redirect URIhttps://auth.aigateway.cequence.ai/v1/outbound/oauth/callback
Auth endpointhttps://accounts.google.com/o/oauth2/v2/auth
Token endpointhttps://oauth2.googleapis.com/token
Scopeshttps://www.googleapis.com/auth/documents, https://www.googleapis.com/auth/documents.readonly, https://www.googleapis.com/auth/drive.file

Available tools

These tools give you programmatic control over document creation, content editing, formatting, and collaboration.

ToolDescription
Create documentCreate a new Google Doc
Get documentRetrieve full document content and structure
Batch updateApply multiple edits in a single request
Insert textAdd text at a specific location in the document
Update textFind and replace content
Apply formattingSet fonts, colors, bold, italic, underline, and alignment
Insert page breakAdd a page break at a specific location
Create tableInsert a table with specified rows and columns
Insert imageEmbed an image from a URL into the document
Add header/footerSet document headers and footers
Create listInsert bulleted or numbered lists
Add commentsAdd comments or suggestions to the document
Manage permissionsShare document with specific users or set view-only access

Tips

Use documents.readonly with drive.readonly when you only need to read or report on documents—this minimizes risk if credentials are compromised.

Construct a template with named ranges or placeholder text, then use batch updates to customize each copy with data from a spreadsheet or database for mail merge and bulk document generation.

Validate that images and external references are accessible before inserting them; a broken image URL in a generated document creates a poor user experience.

Stick to the document's existing named styles rather than inline formatting when applying styles—this keeps the document maintainable and respects any company style guides already applied.

Test your document automation with a test folder first, and require manual review before auto-sharing generated documents with external parties.