How to integrate Google Docs MCP with Claude Code

Manage your Google Docs directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

Get started for freeGet a demo
Google Docs logoGoogle Docs
Oauth2

Google Docs is a cloud-based word processor that enables document creation and real-time collaboration. Its seamless sharing and version history make team editing and content management a breeze.

33 Tools10 Triggers

Introduction

Manage your Google Docs directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate Google Docs with

ChatGPTOpenAI Agents SDKClaude Agent SDKClaude CoworkCodexOpenCodeCursorVS CodeOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAI

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting Google Docs to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

What is the Google Docs MCP server, and what's possible with it?

The Google Docs MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Google Docs account. It provides structured and secure access to your documents, so your agent can create, copy, edit, and organize Google Docs on your behalf.

  • Automated document creation and duplication: Let your agent generate new Google Docs from scratch or copy existing documents to quickly use templates or preserve originals.
  • Rich content editing and formatting: Direct your agent to add headers, footers, footnotes, bullet lists, and more—making it easy to update and format documents programmatically.
  • Targeted content manipulation: Have your agent delete specific content ranges, paragraphs, or sections within any document to keep your files up to date.
  • Named range management: Empower your agent to create and manage named ranges for easier referencing, collaboration, and advanced document workflows.
  • Markdown-based document generation: Allow the agent to create new Google Docs directly from markdown content, streamlining content migration from other tools or sources.

Connecting Google Docs via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here Google Docs) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A Google Docs account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googledocs'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googledocs-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for Google Docs. This URL will be used to connect Claude Code to Google Docs.

What's happening
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for Google Docs
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add Google Docs MCP to Claude Code

bash
claude mcp add --transport http googledocs-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (googledocs-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your Google Docs MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your googledocs-composio entry in the list
  • This confirms that Claude Code can now access Google Docs tools

If everything is wired up, you should see your googledocs-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate Google Docs

The first time you try to use Google Docs tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with Google Docs
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the Google Docs authorization flow
  • Return to the terminal and start using Google Docs through Claude Code

Once authenticated, you can ask Claude Code to perform Google Docs operations in natural language. For example:

  • "Create a new meeting notes document"
  • "Copy last week's project summary template"
  • "Add bullet points to the action items section"

Complete Code

Here's the complete code to get you started with Google Docs and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['googledocs'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http googledocs-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated Google Docs with Claude Code using Composio's MCP server. Now you can interact with Google Docs directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for Google Docs operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various Google Docs operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS & TRIGGERS

Supported Tools and Triggers

Every Google Docs action and event your agent gets out of the box.

Copy Google Document

Tool to create a copy of an existing Google Document.

Create a document

Creates a new Google Docs document using the provided title as filename and inserts the initial text at the beginning if non-empty, returning the document's ID and metadata (excluding body content).

Create Document Markdown

Creates a new Google Docs document, optionally initializing it with a title and content provided as Markdown text.

Create Footer

Tool to create a new footer in a Google Document.

Create Footnote

Tool to create a new footnote in a Google Document.

Create Header

Tool to create a new header in a Google Document, optionally with text content.

Create Named Range

Tool to create a new named range in a Google Document.

Create Paragraph Bullets

Tool to add bullets to paragraphs within a specified range in a Google Document.

Delete Content Range in Document

Tool to delete a range of content from a Google Document.

Delete Footer

Tool to delete a footer from a Google Document.

Delete Header

Deletes the header from the specified section or the default header if no section is specified.

Delete Named Range

Tool to delete a named range from a Google Document.

Delete Paragraph Bullets

Tool to remove bullets from paragraphs within a specified range in a Google Document.

Delete Table Column

Tool to delete a column from a table in a Google Document.

Delete Table Row

Tool to delete a row from a table in a Google Document.

Export Google Doc as PDF

Tool to export a Google Docs file as PDF using the Google Drive API.

Get document by id

Retrieves an existing Google Document by its ID; will error if the document is not found.

Get document plain text

Retrieve a Google Doc by ID and return a best-effort plain-text rendering.

Insert Inline Image

Tool to insert an image from a given URI at a specified location in a Google Document as an inline image.

Insert Page Break

Tool to insert a page break into a Google Document.

Insert Table in Google Doc

Tool to insert a table into a Google Document.

Insert Table Column

Tool to insert a new column into a table in a Google Document.

Insert Text into Document

Tool to insert a string of text at a specified location within a Google Document.

Get Charts from Spreadsheet

Tool to retrieve a list of all charts from a specified Google Sheets spreadsheet.

Replace All Text in Document

Tool to replace all occurrences of a specified text string with another text string throughout a Google Document.

Replace Image in Document

Tool to replace a specific image in a document with a new image from a URI.

Search Documents

Search for Google Documents using various filters including name, content, date ranges, and more.

Unmerge Table Cells

Tool to unmerge previously merged cells in a table.

Update Document Markdown

Replaces the entire content of an existing Google Docs document with new Markdown text; requires edit permissions for the document.

Update Document Section Markdown

Tool to insert or replace a section of a Google Docs document with Markdown content.

Update Document Style

Tool to update the overall document style, such as page size, margins, and default text direction.

Update existing document

Applies programmatic edits, such as text insertion, deletion, or formatting, to a specified Google Doc using the `batchUpdate` API method.

Update Table Row Style

Tool to update the style of a table row in a Google Document.

FRAMEWORKS

How to build Google Docs MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Google Docs MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Google Docs MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Google Docs MCP with Claude Agent SDK

Claude Cowork logo

Claude Cowork

Use Google Docs MCP with Claude Cowork

Codex logo

Codex

Use Google Docs MCP with Codex

Cursor logo

Cursor

Use Google Docs MCP with Cursor

OpenClaw logo

OpenClaw

Use Google Docs MCP with OpenClaw

Hermes logo

Hermes

Use Google Docs MCP with Hermes

CLI logo

CLI

Use Google Docs MCP with CLI

Google ADK logo

Google ADK

Use Google Docs MCP with Google ADK

LangChain logo

LangChain

Use Google Docs MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Google Docs MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Google Docs MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Google Docs MCP with LlamaIndex

CrewAI logo

CrewAI

Use Google Docs MCP with CrewAI

OpenCode logo

OpenCode

Use Google Docs MCP with OpenCode

VS Code logo

VS Code

Use Google Docs MCP with VS Code

FAQ

Frequently asked questions

With a standalone Google Docs MCP server, the agents and LLMs can only access a fixed set of Google Docs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Google Docs and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Google Docs tools.

Yes, absolutely. You can configure which Google Docs scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Google Docs data and credentials are handled as safely as possible.

Start with Google Docs.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Google Docs tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies