Google Docs MCP server — read & write access for agents
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 15 nodes and runs when an MCP client calls one of its tools. Along the way it connects Google Drive and Google Docs.
How it runs
Trigger: When an MCP client calls one of its tools.
No action steps found in the workflow JSON.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (3)
- MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Google Drive Tool
n8n-nodes-base.googleDriveTool - Google Docs Tool
n8n-nodes-base.googleDocsTool
From the author
How it works This workflow creates an MCP server that allows coding agents (e.g. Claude, ChatGPT with MCP support, Clawed Code) to interact with Google Docs programmatically. Many agents today can find files in Google Drive, but cannot open, edit, or format…