How to use Google Docs with Cursor
You want Google Docs inside Cursor so it can find and summarize project documents, turn notes into a polished document, review unresolved document comments, and apply approved edits to a document — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Google Docs gateway
The gateway is the thing Cursor connects to, and it is where you decide which Google Docs tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Google Docs tools
In the dashboard, create a gateway and pick the Google Docs tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your Google Docs tools.
Full Cursor guide in the docs steps verified 2026-08-13
Try these Google Docs prompts
Cursor can now act on your Google Docs account. Click a prompt to copy it.
Use scoped access and permissions to control which documents an agent can reach and which write actions it can take. Pair it with Contextual Access policies so an agent can read source documents without being able to edit, append, or comment.