How to integrate Google Docs MCP with Codex

Framework Integration Gradient
Google Docs Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Google Docs MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Google Docs MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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.

Supported Tools & Triggers

Tools
Triggers
Copy Google DocumentTool to create a copy of an existing google document.
Create a documentCreates 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 MarkdownCreates a new google docs document, optionally initializing it with a title and content provided as markdown text.
Create FooterTool to create a new footer in a google document.
Create FootnoteTool to create a new footnote in a google document.
Create HeaderTool to create a new header in a google document.
Create Named RangeTool to create a new named range in a google document.
Create Paragraph BulletsTool to add bullets to paragraphs within a specified range in a google document.
Delete Content Range in DocumentTool to delete a range of content from a google document.
Delete FooterTool to delete a footer from a google document.
Delete HeaderDeletes the header from the specified section or the default header if no section is specified.
Delete Named RangeTool to delete a named range from a google document.
Delete Paragraph BulletsTool to remove bullets from paragraphs within a specified range in a google document.
Delete TableTool to delete an entire table from a google document.
Delete Table ColumnTool to delete a column from a table in a google document.
Delete Table RowTool to delete a row from a table in a google document.
Get Charts from SpreadsheetTool to retrieve a list of all charts from a specified google sheets spreadsheet.
Get document by idRetrieves an existing google document by its id; will error if the document is not found.
Insert Inline ImageTool to insert an image from a given uri at a specified location in a google document as an inline image.
Insert Page BreakTool to insert a page break into a google document.
Insert Table in Google DocTool to insert a table into a google document.
Insert Table ColumnTool to insert a new column into a table in a google document.
Insert Text into DocumentTool to insert a string of text at a specified location within a google document.
List Charts from SpreadsheetTool to retrieve a list of charts with their ids and metadata from a google sheets spreadsheet.
Replace All Text in DocumentTool to replace all occurrences of a specified text string with another text string throughout a google document.
Replace Image in DocumentTool to replace a specific image in a document with a new image from a uri.
Search DocumentsSearch for google documents using various filters including name, content, date ranges, and more.
Unmerge Table CellsTool to unmerge previously merged cells in a table.
Update Document MarkdownReplaces the entire content of an existing google docs document with new markdown text; requires edit permissions for the document.
Update Document StyleTool to update the overall document style, such as page size, margins, and default text direction.
Update existing documentApplies programmatic edits, such as text insertion, deletion, or formatting, to a specified google doc using the `batchupdate` api method.
Update Table Row StyleTool to update the style of a table row in a google document.

Conclusion

You've successfully integrated Google Docs with Codex using Composio's Rube MCP server. Now you can interact with Google Docs directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Google Docs operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Google Docs operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Google Docs MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Google Docs MCP?

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.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex 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.

Can I manage the permissions and scopes for Google Docs while using Tool Router?

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.

How safe is my data with Composio Tool Router?

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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.