How to use Google Docs with Copilot Studio
You want Google Docs inside Copilot Studio 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 Copilot Studio 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 Copilot Studio
Needs a Microsoft 365 subscription with access to Copilot Studio, plus an Arcade API key.
-
Add an MCP tool to your agent
In Copilot Studio, open your agent → Tools → Add a tool → Model Context Protocol → New tool.
-
Point it at your gateway
Give the server a name and description, put your gateway URL in Server URL, set Authentication to OAuth 2.0 and Type to Dynamic discovery.
-
Authorize and try it out
Saving redirects you to Arcade to approve access. Then start a conversation and use your Google Docs tools — Arcade authorizes each service just in time.
Full Copilot Studio guide in the docs steps verified 2026-08-13
Try these Google Docs prompts
Copilot Studio 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.