By Ira Bodnar, Ryze AI · Updated · Connector tested November 13, 2026
Quick answer
The main way to connect Microsoft Copilot to Google Drive is the Ryze AI connector. Microsoft documents no Copilot chat window that takes an MCP address, so the connector goes onto an agent: connect Google Drive in Ryze AI and attach your files there, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on a Copilot Studio agent, using OAuth 2.0 with Dynamic discovery. The agent can then use 7 Drive tools, limited to files you pick in Ryze AI or files Ryze AI created.
- In Ryze AI open Integrations, find Google Drive under Files and click Connect
- In Ryze AI chat attach the Sheets or Docs the agent should use, with Upload from Drive
- In Copilot Studio open the classic experience, then your agent, Tools, Add a tool, New tool, Model Context Protocol
- Enter the URL, pick OAuth 2.0 with Dynamic discovery, select Create and Next, then create the connection, sign in to Ryze AI and select Add to agent
Microsoft Copilot to Google Drive at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, added as a Model Context Protocol tool on a Copilot Studio agent. A Microsoft 365 Copilot declarative agent can also hold it as an action. Neither route has been run with Ryze AI yet |
| Server address | https://connector.get-ryze.ai/mcp, one address for every user |
| Where the address goes | On an agent. Classic experience: Tools > Add a tool > New tool > Model Context Protocol. New experience: Build tab > Tools > Add > Model Context Protocol (MCP). Microsoft documents no chat window that takes it |
| Sign-ins | Google once, inside Ryze AI, with the drive.file scope. Then Copilot Studio signs in to Ryze AI through OAuth 2.0 Dynamic discovery, so nobody types a client ID or secret |
| Google Drive tools | 7 in total: 3 read and 4 write. None of them deletes a file |
| Files the agent can open | Files attached through the Drive picker in the Ryze AI chat, and files Ryze AI created. The rest of the Drive stays out of sight |
| Can the agent change files | Yes. It can overwrite or append Sheet cells, create Sheets, Docs and text files, and put plain text into a Doc. Copilot Studio switches every tool of a newly added server on |
| Copilot plan | Microsoft's MCP how-to pages name none. A Copilot Studio trial cannot publish, and the Teams plan lists generative orchestration and Power Platform connectors as not available |
| Ryze AI price | Adding the connector costs nothing. The Drive tools run on a plan or trial: Paid Ads is $89 a month after a 7-day free trial |
| Microsoft's and Google's own Drive options | Microsoft: a Google Drive connector for personal accounts on Copilot.com and Copilot Mobile, and a prebuilt Google Drive connector an admin sets up for Microsoft 365 Copilot. Google: a Drive MCP server in Developer Preview whose setup page does not name Copilot |
| Last tested | Connector on November 13, 2026, then 8 Drive tool calls on November 14, 2026, sent from Claude Code. No step ran inside a Microsoft product |
Before you start
- A Copilot Studio agent or a Microsoft 365 Copilot declarative agent. Adding an MCP server is a builder task, usually done by an agent maker or admin in a work or school tenant. Microsoft says all Microsoft 365 users can use Copilot Studio to create agents and actions. A trial account can create and test agents but cannot publish them. Copilot on a personal Microsoft account has no documented place for an MCP server; its own Google Drive connector is covered in the ways section below.
- A Copilot Studio plan that includes connectors. Microsoft says MCP access in Copilot Studio relies on Power Platform connectors. Its licensing page says the Copilot Studio for Teams plan, included in select Microsoft 365 subscriptions, has no Power Platform connectors and no generative orchestration, so those need a standalone subscription. Microsoft does not say whether MCP tools work on the Teams plan, so test before you depend on it.
- A Google account that owns or can open the files. Ryze AI signs in with Google OAuth and the drive.file scope. It works only with files you pick in the Google Drive picker or files Ryze AI created.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; SEO Starter is $129 per month with a 3-day free trial; Agency is $279 per month. Adding the connector is free, and the Drive tools need an active plan or trial.
How to connect Copilot Studio to Google Drive
Steps 1 and 2 happen in Ryze AI, steps 3 to 7 in Copilot Studio. The URL is the same for every user, and the file picker in step 2 decides which files the agent can see.
Connect Google Drive in Ryze AI
Sign in to Ryze AI, open Integrations and find the Google Drive card under Files. Click Connect, sign in with Google and approve access. Ryze AI connects one Google account per workspace for Drive. To use a different account, disconnect and connect again.
Pick the files in Ryze AI chat
Open Ryze AI chat, click + (Add to message), then Attach files, then Upload from Drive, and choose the Sheets, Docs or other files the agent should use. This picker is the only way to make existing files reachable, because the drive.file scope hides everything else. Files that Ryze AI creates are reachable without picking.
Start a new MCP tool on the agent
The steps that follow use Copilot Studio's classic experience. Agents started from the home page now run on the Microsoft Copilot harness, which keeps tools on a Build tab instead of a Tools page, so switch first: select the three dots at the bottom of the home page side bar, then Open classic experience (it lasts for the session), or create the agent through Other ways to build. Open your agent and go to its Tools page. Select Add a tool, then New tool, then Model Context Protocol in the Create new section. The MCP onboarding wizard opens.
Enter the server details
Server name: Ryze AI. Server description: a short note on what the tools do, for example Reads and updates Google Sheets and Docs that the user picked. Microsoft says the agent orchestrator uses this description to decide when to call the server. Server URL: https://connector.get-ryze.ai/mcp.
Choose OAuth 2.0 with Dynamic discovery
Set authentication to OAuth 2.0 and the type to Dynamic discovery. The Ryze AI server supports dynamic client registration, so there is no client ID, secret or callback URL to type in. Select Create, then Next to reach the Add tool dialog.
Create the connection and add the tool
On Add tool, select Create a new connection, or reuse a connection made earlier, and finish the Ryze AI sign-in. Microsoft's page does not describe the sign-in window, and this step was not run for this guide. Then select Add to agent.
Test with a Drive question
Copilot Studio uses MCP only with generative orchestration on, which Microsoft describes as the default. Open the test chat panel and ask: Read the first tab of the Google Sheet I attached in Ryze AI and summarize what the columns hold. If the Drive tools do not run, go through the errors list below.
The Ryze AI help article for Google Drive covers the Drive connection and the file picker. Microsoft's page on connecting an agent to an existing MCP server covers the Copilot Studio wizard, and its page on switching experiences shows how to reach the classic experience. Microsoft pages checked November 14, 2026.
Microsoft 365 Copilot declarative agent
If your people use Microsoft 365 Copilot rather than Copilot Studio, the same URL can become an MCP plugin on a declarative agent. Microsoft describes this in its Agents Toolkit walkthrough.
- In Visual Studio Code, make sure Microsoft 365 Agents Toolkit is version 6.12.0 or later.
- Select the Agents Toolkit icon in the Activity Bar, choose Create a New Agent/App, then Declarative Agent.
- Choose Add an Action, then Start with an MCP Server, and paste https://connector.get-ryze.ai/mcp.
- Select OAuth (with dynamic registration), then set a project location and an agent name. Among Microsoft's conditions for this option is a client secret that the authorization server issues at registration; whether the Ryze AI server issues one to Microsoft was not checked.
- In the Accounts pane, sign in to Microsoft 365 and check that Custom App Upload Enabled and Copilot Access Enabled both appear. If not, ask an admin to allow custom app upload.
- In the Lifecycle pane select Provision, read the dialog, select Confirm and wait until the toolkit reports that provisioning is done.
- Open m365.cloud.microsoft/chat, find the agent whose name ends in dev under Agents in the sidebar, ask a Drive question and select the Sign in to button that carries the agent's name.
Microsoft says the toolkit sets up dynamic tool discovery, so the agent resolves the server's tools at run time. Sideloading requires an admin to turn on Upload custom apps in the Teams admin center. Before the agent sends anything to the plugin for the first time, Copilot asks the person to allow it.
Sources: Build a plugin for a declarative agent from an MCP server, dynamic client registration for plugins, extensibility requirements, plugin overview. Checked November 14, 2026.
Copilot and MCP: what Microsoft documents
| Topic | What Microsoft's pages say |
|---|---|
| Where an MCP address is accepted | In builder and admin tools only: Copilot Studio (the MCP onboarding wizard in the classic experience, the Add MCP server page in the new one), a declarative agent action in Agents Toolkit, a plugin package manifest, or a custom federated connector in the Microsoft 365 admin center. Plugins made from MCP servers are not offered as standalone experiences in Microsoft 365 Copilot |
| Two Copilot Studio experiences | The home page now builds agents on the Microsoft Copilot harness. The wizard with Dynamic discovery belongs to the standard harness, opened per session with Open classic experience. The how-to page for the new flow is labeled preview and does not list its sign-in choices |
| Config files and local servers | Copilot Studio is set up in the browser, and no page names a settings file for it. Agents Toolkit generates ai-plugin.json, and the m365agents.yml project file carries isPKCEEnabled. No route starts a local command: Microsoft 365 Copilot must reach the server over the internet, and Microsoft points developers with a local server to a dev tunnel |
| Transport | Copilot Studio takes Streamable only and dropped SSE after August 2025. Plugin packages and Cowork expect Streamable HTTP on HTTPS with TLS 1.2 or later |
| Sign-in in Copilot Studio | The wizard offers None, API key or OAuth 2.0, and OAuth 2.0 comes as Dynamic discovery, Dynamic or Manual. Microsoft calls Dynamic discovery the simplest. A tool runs on End user credentials unless the maker picks Maker-provided credentials |
| Sign-in in a declarative agent | Entra single sign-on, dynamic client registration, the OAuth 2.0 authorization code flow or none. MCP plugins take no API keys, PKCE is on by default, and dynamic registration needs a client secret from the authorization server |
| Approval before a tool runs | Copilot Studio turns on every tool of an added server through Allow all. A declarative agent asks before its first data goes to a plugin, then before each tool that changes data, unless the person chose always allow |
| Plan and billing | No plan on the MCP how-to pages. New-experience agents are billed in Copilot Credits, which count model tokens, the harness and tool use, MCP servers included |
| Reaching people in Teams and Copilot | Publish the Copilot Studio agent once, then connect the Teams and Microsoft Copilot channels. A trial license cannot publish |
| Where servers are managed | Classic: select the server on the agent's Tools page for its Details, Tools and Resources and an Enabled switch. New: the tools list on the Build tab. Sideloaded agents: Teams > Apps > Manage your apps |
| Admin controls | A Power Platform data policy on connectors also covers MCP servers, and a blocked tool shows as disabled. In the Microsoft 365 admin center, Agents > Tools > Registry can block a server and with it every tool it exposes |
Sources: MCP servers in the new experience, switching experiences, MCP in Copilot Studio, MCP tools on an agent, agent tools and credentials, managing tools in the new experience, Teams and Microsoft Copilot channels, Copilot Credits, plugin sign-in types, local servers and dev tunnels, MCP servers in plugin packages, Cowork plugin requirements, custom federated connectors, admin tool registry. Checked November 14, 2026.
Other AI clients
The same URL works in other MCP clients. Ryze AI has Google Drive guides for these:
What the agent can reach in Drive
Two sign-ins decide what the agent can touch.
- Google sign-in in Ryze AI
- Google OAuth on your account with the drive.file scope. Google describes drive.file as access to files you open with an app or share with it through the file picker, plus files the app creates. Ryze AI therefore sees only picked or self-created files.
- Ryze AI sign-in from Copilot
- The Copilot connection signs in to Ryze AI with OAuth 2.0. Copilot Studio runs the tool on End user credentials unless the maker switches to Maker-provided credentials, so each person who chats with the agent makes their own connection. The agent then reaches the Drive files that the Ryze AI workspace can reach, and no others.
- Files outside the picker
- A file you did not pick and Ryze AI did not create is invisible to the tools, including when the call comes from a Copilot agent. Pick it in Ryze AI chat first.
- Power Platform data policy
- Microsoft notes that a data policy for Power Platform connectors also governs the MCP server and its tools for your agent. If a policy blocks it, ask your Power Platform admin.
Sources: Google's Drive scopes page, Microsoft's MCP server and data policies note and its tool credentials page, checked November 14, 2026, and the Ryze AI Google Drive integration.
One Google scope, and the ones left out
Drive access is granted once, by a Google sign-in inside Ryze AI. The connection holds a single Google scope, with no API key, service account or Drive role behind it. A Copilot agent never signs in to Google on this route; it signs in to the connector. The table sets that one scope beside the broader Google scopes the connection leaves out.
| Scope | Google's label and meaning | For a Copilot agent |
|---|---|---|
| drive.file | Non-sensitive, and recommended by Google for most uses. Covers files a person opens with the app or hands to it through a picker, plus files the app makes | Held. The agent works on the Sheets and Docs you attached in Ryze AI and on files Ryze AI made |
| drive.readonly | Restricted. Viewing and downloading every Drive file | Not held, so a request like find my budget files cannot search the Drive |
| drive | Restricted. Full management of every Drive file | Not held |
| drive.metadata.readonly | Restricted. Metadata of every file in the Drive | Not held, so even the names of unpicked files stay hidden |
| spreadsheets and documents | Sensitive. Every Sheet or every Doc of the account, deleting included | Not held. A picked Sheet still opens with all its tabs, because Google applies Sheets scopes to the whole file |
| mcp:read and mcp:write | Not Google scopes: the Ryze AI connector's own, named in its discovery files on November 13, 2026 | Part of the sign-in that Copilot runs against the connector. Which of the two a Copilot connection receives was not tested |
Left off the connection: every scope that lists, searches or reads the whole Drive. In practice a Copilot agent cannot find a file by itself, cannot open a file a colleague shared with you until you pick it, and cannot delete anything, because no Ryze AI tool deletes even though Google's drive.file wording would allow it for the app's own files. Google's own Drive MCP server takes drive.readonly next to drive.file, which is why it can reach every file the user can open.
Sources: Drive API scopes, Sheets API scopes, Docs API scopes, Google Picker overview. Checked November 14, 2026.
Removing access
To take Drive away from a Copilot Studio agent in the classic experience, open its Tools page, hover over the Ryze AI server, choose the three dots and Delete, or open the server, switch Enabled off and Save. In the new experience, select the X beside the server on the Build tab, then Remove; Microsoft notes the underlying server configuration is kept. A sideloaded declarative agent is managed in Teams under Apps > Manage your apps. To cut Ryze AI off from Drive itself, disconnect Google Drive under Integrations in Ryze AI or revoke the app in your Google account permissions.
Tools Copilot gets for Google Drive
The Ryze AI connector exposes 7 Google Drive tools: 3 read and 4 write. There is no delete tool. Copilot Studio adds the server to the agent as a single tool with every one of its tools switched on, the 7 Drive tools included; turn Allow all off to switch single tools off. If your Ryze AI sign-in covers more than one workspace, every Drive tool also asks for a workspace argument.
| Tool | Type | What it does |
|---|---|---|
| google_drive__listFiles | Read | Lists the Google Drive files the app can access, newest first, with an optional Drive search filter. |
| google_drive__readFile | Read | Reads a Drive file by ID: Sheets return cell values, Docs and Slides return plain text, and text, CSV and JSON files return their content. |
| google_drive__getSheetValues | Read | Reads cell values from a Google Sheet range or tab. |
| google_drive__updateSheetValues | Write | Overwrites cell values in a Google Sheet range; formulas are allowed. |
| google_drive__appendSheetValues | Write | Appends rows after the last row of a table in a Google Sheet. |
| google_drive__createFile | Write | Creates a new Google Sheet, Google Doc, or text, CSV or JSON file in your Drive and returns its link. |
| google_drive__writeDoc | Write | Writes plain text into a Google Doc, appended at the end or replacing the whole document. |
Limits to plan around: Doc writes are plain text with no headings, links or formatting. Images picked from Drive are not supported. Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides are attached by name only.
Whether the agent pauses before a write depends on where it runs. In the classic experience every tool of the server starts on, and switching Allow all off is how you keep updateSheetValues or writeDoc away from the agent. Microsoft also describes a per-tool option, Ask the end user before running, that defaults to No, but its page does not say the option appears for an MCP server, so look for it on the Ryze AI server before you rely on it. The new-experience pages describe only on and off toggles. A declarative agent asks the first time it sends data to the plugin, then before tools that change data. The Ryze AI chat has its own Tool approvals picker, which starts on Skip all approvals and can be set to Approve write & delete or Manual approve; whether that picker also holds calls that come from a Copilot agent is not documented. The write tools can overwrite cells and replace a whole Doc, so try them first on a copy of a file.
Limits in numbers
The Ryze AI tools, Copilot and Google each cap something on this route. The Google rows are Google's published ceilings for its own APIs. Which quota set covers the Google Cloud project behind the Ryze AI connection, and which Google API each Drive tool calls, was not checked, and none of the test answers carried a quota figure.
| Limit | Figure | Set by |
|---|---|---|
| Rows in one Sheet read | 10,000 per getSheetValues call. Later rows need explicit row numbers, such as A10001:D20000 on the same tab | Ryze AI tool definition |
| Largest file readFile returns | 10 MB. Bigger files, binary files and other Google formats come back as metadata with content set to null | Ryze AI tool definition |
| Input lengths | File, spreadsheet and document IDs 1 to 200 characters; ranges up to 300; a listFiles filter or page token up to 500; createFile and writeDoc content up to 200,000 | Ryze AI tool definitions |
| Tools on one Copilot Studio agent | 128 with generative orchestration, and Microsoft advises keeping to 25 to 30. The Ryze AI server counts as one tool; Microsoft does not say whether the tools inside it count toward 128 | Microsoft, classic experience |
| MCP servers at the same time | A new-experience agent can hold several, but only a capped number run in one conversation and the others sit out that turn. Microsoft prints no figure | Microsoft, new experience |
| Plugins and tools in a declarative agent | Up to 5 plugins always go into the prompt; past 5, Copilot picks by the plugin description. Answers may get worse past 10 functions or tools in one plugin | Microsoft 365 Copilot |
| Tool list changes | Copilot Studio picks up server changes by itself. Behind a republished custom connector, new or renamed tools can take about 12 to 24 hours, with no manual refresh | Microsoft |
| Drive API quota | 1,000,000 quota units a minute per Cloud project and 325,000 per user per project, for projects created on or after May 1, 2026 | |
| Quota units per Drive API call | 5 to read, 100 to list, 50 to edit, 200 to download or export | |
| Past the Drive quota | 403: User rate limit exceeded, or 429: Rate limit exceeded. Google advises truncated exponential backoff, usually capped at 32 or 64 seconds | |
| Sheets API | 300 reads and 300 writes a minute per project, 60 of each per user per project, then 429: Too many requests. A request still processing after 180 seconds times out | |
| Docs API | Reads: 3,000 a minute per project and 300 per user. Writes: 600 and 60 | |
| Google file sizes | Docs up to 1.02 million characters; Sheets up to 20 million cells or 100 MB | |
| Undoing a write | Restore an earlier version from version history. Drive help says a stored version might be deleted after 30 days or once 100 newer versions exist |
Sources: Drive API usage limits, Sheets API limits, Docs API limits, Drive file sizes, Drive file versions, Copilot Studio tool limits, MCP servers per conversation, declarative agent plugin limits, Copilot Studio MCP troubleshooting. Checked November 14, 2026.
Drive calls through the connector, tested November 14, 2026
No Copilot agent was built for this guide, so the 8 Drive calls of November 14, 2026 went through the Ryze AI connector from Claude Code. Every request was chosen so that no real file could come back: one list that matched nothing, and seven calls meant to be refused so their messages could be recorded.
| What the call asked | Tool | What came back |
|---|---|---|
| Files whose name holds a random 20-letter string | google_drive__listFiles | Worked: {"files":[]}, with no page token and no quota field |
| A file ID that does not exist | google_drive__readFile | Status not_found, with a File not found message |
| Cells Sheet1 A1:B2 of a spreadsheet ID that does not exist | google_drive__getSheetValues | Status not_found |
| The same no-match filter plus a field Drive does not have | google_drive__listFiles | Error 400, Invalid Value, location q |
| The no-match filter with a page token that no list call issued | google_drive__listFiles | Error 400, Invalid Value, location pageToken |
| A file ID 201 characters long | google_drive__readFile | invalid_arguments, maximum 200. Stopped by the connector; Google was never called |
| A no-match filter 501 characters long | google_drive__listFiles | invalid_arguments, maximum 500. Stopped by the connector |
| An empty range on a made-up spreadsheet ID | google_drive__getSheetValues | invalid_arguments, minimum 1. Stopped by the connector |
First 3 prompts to run
Answers come from your own files, so this page describes what comes back instead of showing sample output. Paste a prompt into the test chat or the agent's instructions.
1. Read a keyword list from a Sheet
Read the keyword list on the first tab of the Google Sheet I picked in Ryze AI and group the keywords by theme.
Tools used: google_drive__listFiles, google_drive__getSheetValues
What comes back: The cell values from the tab, grouped into themes in the reply. The Sheet itself is not changed.
2. Write a report into a Doc
Create a new Google Doc called Weekly report and write a plain-text summary of the Sheet I picked into it. Give me the link when it is done.
Tools used: google_drive__readFile, google_drive__createFile, google_drive__writeDoc
What comes back: A new Doc in your Drive with plain text only, and its link in the reply.
3. Add rows to a table
Append these three rows after the last row of the table on the Results tab of my picked Sheet, then read the tab back to confirm.
Tools used: google_drive__appendSheetValues, google_drive__getSheetValues
What comes back: The new rows added under the existing table, followed by the tab's values so you can check them.
Ryze AI has not run this route inside Copilot Studio or Microsoft 365 Copilot. The steps come from Microsoft's documentation and from the connector's sign-in metadata, which offers dynamic client registration. If what you see in Copilot differs, tell Ryze AI support.
10 jobs to hand to a Copilot agent
Ten jobs for a Copilot agent that holds the Ryze AI tool, each with the tool that does it. None was run on a real file for this guide, so the last column comes from the tool definitions and the Ryze AI help center. Every job needs an active Ryze AI plan or trial. A job on an existing file needs that file picked in Ryze AI first or made by Ryze AI, and the write jobs also depend on which tools the agent has switched on.
| Job | Ask the agent | Tool | Works on the default connection |
|---|---|---|---|
| Theme a keyword list | Group the keywords on the first tab of the Sheet I attached in Ryze AI by theme. | google_drive__getSheetValues | Yes, up to 10,000 rows per call |
| Check what the agent can open | Which Drive files can you reach? List them newest first. | google_drive__listFiles | Yes, picked files and Ryze AI files only |
| Brief to bullet points | Turn the brief in the Doc I attached into five bullet points. | google_drive__readFile | Yes, read as plain text |
| Deck summary | Summarize the text of each slide in the Slides file I attached. | google_drive__readFile | Yes, slide text only |
| Inspect an export | Which columns does the CSV I attached have, and what does each hold? | google_drive__readFile | Yes, files up to 10 MB |
| Weekly report in a Doc | Create a Doc named Weekly report and write a plain-text summary of this conversation into it. | google_drive__createFile, then google_drive__writeDoc | Yes, without headings or formatting |
| Log new rows | Append today's three findings as rows under the table on the Log tab. | google_drive__appendSheetValues | Yes, on a picked or Ryze AI made Sheet |
| Refresh a block of cells | Overwrite B2:E12 on the Summary tab with these values and formulas. | google_drive__updateSheetValues | Yes. The range must match the values, and the old cells are replaced |
| New tracker Sheet | Make a new Sheet called Tracker and fill it with this table. | google_drive__createFile, then google_drive__updateSheetValues | Yes, in two calls, and the link comes back |
| Clean up old drafts | Delete last month's draft Docs. | None | No. No Ryze AI tool deletes, and files nobody picked stay hidden |
4 ways to connect Microsoft Copilot to Google Drive
Four ways put Google Drive in front of Microsoft Copilot, and each has a vendor page that names a Copilot product. This guide uses the Ryze AI connector as the main way: it puts 7 Drive tools, 4 of them writers, on an agent you build, with Google signed in once inside Ryze AI and no Google Cloud project of your own. All four are described from their own pages, and none of them was set up inside Copilot for this guide.
| Way | Runs where | Setup in Microsoft Copilot | What it reaches in Drive | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | Copilot Studio, classic experience: the MCP wizard with the connector URL and OAuth 2.0 Dynamic discovery, then a new connection and Add to agent. Declarative agent: Start with an MCP Server and OAuth (with dynamic registration), where Microsoft's client secret condition was not checked for Ryze AI | 7 tools on picked or Ryze AI made files: read Sheets, Docs, Slides and text, CSV or JSON files; overwrite or append Sheet cells; create files; plain-text Doc writes. No search of the whole Drive, no delete | Connector free to add. Paid Ads $89 a month after a 7-day free trial, Agency $279 a month |
| Google Drive connector for personal accounts, by Microsoft | Inside Copilot.com and Copilot Mobile on iOS and Android, for personal Microsoft accounts | Under Profile > Connectors, where Microsoft's support article lists Google Drive next to OneDrive, Outlook.com, and Gmail with Google Calendar and Contacts. The article mentions no MCP and no way to add a connector of your own | The article names the service. What Copilot can read or change in Drive through it was not recorded for this guide | Not recorded for this guide |
| Prebuilt Google Drive connector for Microsoft 365 Copilot, by Microsoft | Inside Microsoft 365: a synced connector indexes the Drive content into Microsoft Graph | An admin sets up the prebuilt Google Drive connector in the Microsoft 365 admin center. Microsoft lists Google Drive among its prebuilt file-sharing connectors | Drive content made findable in Copilot and Microsoft Search for the people the admin allows, with Drive's own sharing permissions respected. Microsoft states that Copilot Chat is read-only by default | Not recorded for this guide |
| Zapier MCP | Hosted by Zapier | Zapier's quickstart lists Microsoft Copilot Studio among its MCP clients and says any client with Streamable HTTP works. Generate a Zapier MCP URL, choose Google Drive actions, then add the URL as an MCP tool on the agent. The Zapier pages give no Copilot Studio steps, and the pairing was not tried | The Drive actions you switch on. Zapier's Drive page shows 8 before Load More: Copy File, Delete File (Permanent), Export File, Upload File, Create Folder, Move File, Create File From Text and Remove File Permission. Enterprise app and action restrictions are not supported yet | Each successful tool call uses 2 tasks from your Zapier plan; failed calls use none |
Microsoft says that when Copilot Studio reaches tools and resources through a non-Microsoft MCP server, responsibility for them sits with you. That holds for the Ryze AI connector and for Zapier alike.
Drive options that do not fit a Copilot agent
- Google's Drive MCP server, at https://drivemcp.googleapis.com/mcp/v1 in the Google Workspace Developer Preview Program. Its setup page walks through Antigravity and Claude (Enterprise, Pro, Max or Team), plus an Others section that names no product; Microsoft Copilot is not named. It needs a Google Cloud project with the Drive API and Drive MCP API enabled, the drive.readonly and drive.file scopes, and a web OAuth client marked Use this client for an AI-powered agent, which Google enforces from November 11, 2026. Copilot Studio's Manual OAuth type takes a client ID and secret and hands back a callback URL, but that pairing was not tried. Its 8 tools are search_files, list_recent_files, read_file_content, download_file_content, get_file_metadata, get_file_permissions, create_file and copy_file, with no delete, move, rename or share tool.
- Google's Sheets, Docs and Slides MCP servers, in Developer Preview since July 13, 2026, for cell-level reads and edits. Their setup pages name the same apps: Antigravity, Claude and an unnamed Others group.
- Microsoft's federated connectors. The federated connector list on Microsoft's overview page includes Gmail, Google Calendar and Google Contacts. Google Drive is not on it.
- A custom federated connector pointed at Ryze AI. An admin can turn an MCP address into a connector in the Microsoft 365 admin center, and people with a Microsoft 365 Copilot license then connect it under Settings > Sources. Its sign-in methods are Microsoft Entra SSO, OAuth 2.0 with a client registered by hand in the Teams Developer Portal, or No Auth. The Ryze AI connector lets clients register themselves through its register endpoint, a method that list leaves out, and this guide has no fixed client ID and secret to enter instead, so the route is not confirmed for Ryze AI.
- Drive apps built into other assistants. Anthropic's Google Drive connector serves Claude and Claude Desktop, OpenAI's Google Drive app serves ChatGPT, Gemini's Google Workspace app serves Gemini, and the Google Workspace extension names Gemini CLI only.
- Composio. A hosted toolkit with 92 Drive tools and 7 triggers. Its page names Claude, Claude Code, ChatGPT, Cursor, Claude Cowork, Antigravity, Codex, VS Code, Grok Bot, Grok Build, Muse, OpenCode, OpenClaw and Hermes, and Microsoft Copilot is not among them.
- google_workspace_mcp, open source. A Python server you run yourself. Its README names Claude, Claude Code, ChatGPT in Developer Mode, Codex, VS Code, LM Studio and Open WebUI, not Copilot, though it says any MCP client works over streamable HTTP. Copilot could only reach it at a public HTTPS address.
- Google Workspace CLI (gws), a command-line tool with agent skills and no MCP server. Its README names Gemini CLI and OpenClaw and says it is not an officially supported Google product.
- @modelcontextprotocol/server-gdrive, the MCP project's old reference Drive server, which npm marks as no longer supported.
Which one to pick
Ryze AI is the best way to connect Microsoft Copilot to Google Drive when a Copilot Studio agent has to write results back into Sheets and Docs you choose, with three caveats: nobody has run this route inside Copilot yet, the agent sees only files picked in Ryze AI or made by it, and Doc writes are plain text with no delete tool. For questions across a whole company Drive, Microsoft's prebuilt Google Drive connector fits better, because an admin indexes the content for Copilot and Microsoft Search and each person sees only what Drive lets them open. On a personal Microsoft account, the Google Drive connector under Profile > Connectors is the documented route, since personal Copilot has no documented place for an MCP address. Zapier MCP suits a team whose Drive automations already run in Zapier and that wants file actions such as copy, move or upload.
Sources: Copilot Studio MCP guide, non-Microsoft MCP servers in Copilot Studio, declarative agents with MCP, custom federated connectors, Copilot connectors for personal accounts, Zapier MCP for Google Drive, Zapier MCP quickstart, Google Drive MCP server setup, Google Drive MCP reference, Google Workspace MCP servers, Google Workspace Developer Preview Program, Composio Google Drive toolkit, Anthropic's Google Workspace connectors, OpenAI's Google Drive app, Gemini and Google Workspace, Workspace extension for Gemini CLI, google_workspace_mcp, Google Workspace CLI, @modelcontextprotocol/server-gdrive on npm. Checked November 14, 2026.
Microsoft's connector lists: Copilot connectors overview, Federated connectors overview. Checked November 15, 2026.
The Ryze AI Google Drive integration page describes the Ryze AI side of the main way.
Copilot, Google Drive and MCP: dates that matter
| Date | What happened |
|---|---|
| November 19, 2024 | @modelcontextprotocol/server-gdrive 0.1.0, the MCP project's reference Drive server, went up on npm. Google did not make it, and npm now marks the package as no longer supported. |
| March 19, 2025 | Copilot Studio got its first MCP support, which ran over SSE at the time. Microsoft later called that release a public preview. |
| May 29, 2025 | Microsoft made MCP in Copilot Studio generally available and added streamable transport, with SSE still in public preview. Microsoft's how-to page now says SSE is not supported after August 2025. |
| December 15, 2025 | MCP support in Microsoft 365 Copilot declarative agents reached general availability, set up through Add Action and Start with an MCP server in Agents Toolkit. |
| April 22, 2026 | Google put its Drive MCP server into developer preview, on the same day as its Gmail, Calendar and Chat servers. |
| May 1, 2026 | Google opened Workspace MCP to public developer preview. Cloud projects created from this day count Drive API use in quota units. |
| July 13, 2026 | Google's Docs, Sheets and Slides MCP servers joined the developer preview. |
| July 15, 2026 | Microsoft 365 Copilot release notes: admins can deploy federated, MCP-based connectors from the Connectors tab under Copilot, and agents built with MCP work in Word, Excel, PowerPoint and Outlook. |
| September 2, 2026 | A Microsoft blog post declared the harness now named the Microsoft Copilot harness generally available in Copilot Studio, with MCP servers as tools. Microsoft's how-to page for that flow still says preview. |
| October 27, 2026 | Microsoft 365 Copilot release notes list custom MCP connectors that admins create in the Microsoft 365 admin center. The roadmap item for the feature gives February 2026 as its availability month. |
| November 11, 2026 | Google's release notes set this day for its Workspace MCP servers to start rejecting requests from OAuth clients not marked as agentic. |
Sources: @modelcontextprotocol/server-gdrive on npm, Microsoft Copilot blog, March 19, 2025, Microsoft Copilot blog, May 29, 2025, Copilot Studio MCP guide, Microsoft 365 Developer Blog, December 15, 2025, Google Workspace developer release notes, Google Workspace Updates blog, May 2026, Drive API usage limits, Microsoft 365 Copilot release notes, Microsoft Copilot blog, September 2, 2026, MCP servers in the new experience, Microsoft 365 roadmap item 501585. Checked November 14, 2026.
How this guide was tested
Two rounds of checks sit behind this guide: the connector itself on November 13, 2026 and eight Google Drive tool calls on November 14, 2026. Microsoft's, Google's and the other vendors' pages were read on November 14, 2026.
| What was run | What came back |
|---|---|
| A request to the connector address with no sign-in (November 13) | HTTP 401 from https://connector.get-ryze.ai/mcp, with a WWW-Authenticate header pointing to the sign-in details. |
| The two discovery files on the connector's host (November 13) | Both loaded. They name the authorize, token and register endpoints, the authorization code and refresh token grants, PKCE with S256, and the scopes mcp:read and mcp:write. Microsoft's dynamic registration for declarative agents asks for this kind of metadata and a register endpoint; whether a client secret comes back was not checked. |
| The Drive tool list (November 14) | The 7 google_drive tools named in the tools table, every definition loaded, and no other Drive tool. |
| Eight Drive calls sent from Claude Code (November 14) | Five reached Google: one empty list, two not_found and two Error 400 answers. The connector stopped the other three on input length before Google was called. |
| The tool definitions (November 14) | The 10,000-row, 10 MB and input-length figures in the limits table above. |
Not run for this guide: any step inside a Microsoft product. No Copilot Studio agent was created, no MCP tool was added, no Agents Toolkit project was provisioned, no admin center connector was set up, and no Ryze AI sign-in was made from Copilot. Those steps follow Microsoft's pages as read on November 14, 2026. The Drive calls came from Claude Code, not from a Copilot agent. No real Drive file was listed or read, so no Sheet values or Doc text came back, and none of the 4 write tools ran, because they change files.
Errors and fixes
Exact Drive messages from the test
These are the messages the connector and Google sent back to the calls of November 14, 2026, word for word except the file ID. Both Error 400 answers read Invalid Value; the location after the comma is a separate field of the error.
| Message | What it means | What to do |
|---|---|---|
| File not found: [file ID]. | readFile could not open that ID. Under drive.file, a file nobody picked in Ryze AI looks exactly like a missing one, and Google uses the same words for its 404 error. | Attach the file in the Ryze AI chat with + > Attach files > Upload from Drive, then ask the agent again. |
| Requested entity was not found. | getSheetValues got a spreadsheet ID that is wrong or outside what the connection reaches. | Pick the Sheet in Ryze AI, or ask the agent to run listFiles and reuse an ID from that list. |
| Invalid Value, location q | The listFiles search filter is not valid Drive query syntax; in the test it named a field Drive lacks. | Tell the agent to filter with name contains and one word, or to list without a filter. |
| Invalid Value, location pageToken | The page token was not issued by an earlier list call. | Ask for the list again from the first page. |
| Too big: expected string to have <=200 characters | A file ID longer than 200 characters, usually a whole link passed as the ID. The connector refused it before calling Google. | Give only the ID, the part of the link between /d/ and /edit. |
| Too big: expected string to have <=500 characters | The listFiles filter ran past 500 characters. | Ask for one short condition. |
| Too small: expected string to have >=1 characters | getSheetValues received an empty range. Named ranges are not accepted either. | Give a tab name such as Sheet1, or a range such as A1:D50 on that tab. |
Google's wording for the 404 error: Drive API error handling. Checked November 14, 2026.
Other problems
- There is no place to paste the URL in Copilot chat
- No Copilot chat window has a documented field for an MCP address. Put the URL on a Copilot Studio agent, or build a declarative agent in Agents Toolkit. An admin can also turn an MCP address into a custom federated connector, but its sign-in methods leave out dynamic registration, so that route is not confirmed for Ryze AI. On a personal account, use the Google Drive connector under Profile > Connectors instead.
- The Tools page or the New tool button is missing
- The agent was built on the new experience, which keeps tools on the Build tab. Open the classic experience from the three dots at the bottom of the home page side bar, or create the agent through Other ways to build.
- I cannot publish the agent
- A Copilot Studio trial lets you create and test agents but not publish them. Use the test chat, or move to a plan that can publish.
- Model Context Protocol is missing on the Teams plan
- The Copilot Studio for Teams plan has no Power Platform connectors or generative orchestration, and MCP access relies on connectors. Ask your admin about a standalone Copilot Studio subscription.
- The connector is blocked
- A Power Platform data policy that regulates connectors also regulates the MCP server, and a blocked tool shows as disabled in the Add tool panel. Ask your Power Platform admin to allow it. An admin can also block a server under Agents > Tools > Registry in the Microsoft 365 admin center, or hold a restricted tool until a request is approved under Agents > Tools > Requests.
- Agents Toolkit says custom app upload is off
- An admin must turn on Upload custom apps in the Teams admin center. Ask them, then reload the Accounts pane.
- The declarative agent sign-in does not finish
- Microsoft's dynamic registration for declarative agents requires the authorization server to issue a client secret, and registration without one is not supported yet. That was not checked for the Ryze AI server, so fall back to the Copilot Studio route if the sign-in stalls.
- The agent never calls the Drive tools
- Microsoft says the orchestrator reads the server description to decide when to call it. Rewrite the description to say that the tools read and write Google Sheets and Docs, and check that generative orchestration is on.
- The agent cannot find my file
- The drive.file scope hides files you did not pick. In Ryze AI chat use + > Attach files > Upload from Drive, then ask again.
- The tool list is missing Drive tools
- If you added the connector before connecting Google Drive, remove it from the agent and add it again so the tool list refreshes. Copilot Studio picks up server changes on its own, but behind a republished custom connector, tool changes can take about 12 to 24 hours.
- The tools return a subscription message
- The Drive tools need an active Ryze AI plan or free trial, and Google Drive must show as connected under Integrations in Ryze AI.
- An attached file is read by name only
- Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides are attached by name only. Export the content to a Sheet, Doc or CSV.
- I need a second Google account
- Drive connects one Google account per workspace. Disconnect and connect again with the other account, or use a separate Ryze AI workspace.
Terms on this page
- Copilot Studio agent
- An assistant built in Microsoft's web tool and given tools, such as an MCP server. People reach it in Teams and Microsoft Copilot once it is published to those channels.
- Classic and new experience
- Copilot Studio's two ways of building agents. The classic one runs on the standard harness, home of the MCP wizard; the new one runs on the Microsoft Copilot harness, where new agents start.
- Dynamic discovery
- The Copilot Studio OAuth 2.0 choice for servers with dynamic client registration: Studio looks up the sign-in endpoints and registers itself.
- Declarative agent
- A Microsoft 365 Copilot agent defined by a manifest, built here in Agents Toolkit, that can carry an MCP server as an action.
- drive.file scope
- Google's Drive permission for files a person opens with an app or hands to it through a picker, plus files the app creates.
- Google Picker
- Google's file-open dialog for Drive. In Ryze AI it opens from + > Attach files > Upload from Drive.
- File ID
- The string between /d/ and /edit in a Drive link, which the Drive tools take instead of a file name. Google says a spreadsheet ID stays the same when the file is renamed.
Sources: publishing to Teams and Microsoft Copilot, Copilot Studio experiences, Dynamic discovery, declarative agents with MCP, drive.file, Google Picker, spreadsheet IDs. Checked November 14, 2026.
Frequently asked questions
How do I connect Microsoft Copilot to Google Drive?
Ryze AI is the best Google Drive MCP option for a Copilot agent that must edit Sheets and write Docs, though it only reaches files you pick and Ryze AI has not tested it in Copilot Studio. Connect Google Drive in Ryze AI, then add https://connector.get-ryze.ai/mcp as a Model Context Protocol tool on a Copilot Studio agent in the classic experience, with OAuth 2.0 and Dynamic discovery.
Is there a Google Drive MCP server for Copilot?
Yes, the Ryze AI connector at https://connector.get-ryze.ai/mcp is a hosted Google Drive MCP server that you add as a tool on a Copilot Studio agent, with 7 tools for the files you pick; Ryze AI has not yet run it inside Copilot Studio. Google's own Drive MCP server is in Developer Preview, and its setup page names Antigravity and Claude rather than Copilot. Zapier MCP lists Copilot Studio as a client and offers Drive file actions.
What does a Google Drive MCP server do?
It hands an AI assistant a set of Google Drive tools over the Model Context Protocol, so the assistant can list, read or write files when you ask. Through Ryze AI those tools read the Sheets, Docs, Slides and text files you picked, change Sheet cells, create files and write plain text into Docs.
Can I use the same Google Drive MCP server in Claude Code?
Yes, the Ryze AI connector serves the same 7 Drive tools in Claude Code, and the Drive test calls behind this guide were sent from Claude Code. The Claude Code guide for Google Drive has the setup command.
Is there a Google Drive connector for Copilot?
Yes, Microsoft offers two. Personal accounts get a Google Drive connector under Profile > Connectors on Copilot.com and Copilot Mobile, and an admin can set up Microsoft's prebuilt Google Drive connector in the Microsoft 365 admin center to index Drive content for Microsoft 365 Copilot and Microsoft Search. Microsoft's federated connector list has Gmail, Google Calendar and Google Contacts but no Google Drive. The Ryze AI connector is a separate route, added to an agent as an MCP tool.
Can I paste an MCP URL into the Copilot chat app?
No. Microsoft's pages show no chat window that accepts an MCP address. The URL goes on a Copilot Studio agent, into a declarative agent built with Microsoft 365 Agents Toolkit, or into a custom federated connector that an admin creates, a route not confirmed for Ryze AI.
Can Copilot see all my Google Drive files?
No. Ryze AI uses the drive.file scope, so the tools reach only files you pick in the Drive picker in Ryze AI chat and files Ryze AI created. They do not search your whole Drive.
What can Copilot do with Drive through Ryze AI?
Read Sheets, Docs, Slides and text, CSV or JSON files; update cells or append rows in a Sheet; create new Sheets, Docs and text files; and write plain text into a Doc. There is no delete tool.
Which Copilot plan do I need?
Microsoft says all Microsoft 365 users can use Copilot Studio to create agents. A trial can create and test but not publish. MCP access relies on Power Platform connectors, which the Teams plan lacks, so plan for a standalone subscription. Declarative agents also need an admin to allow custom app upload.
Does the Ryze AI connector work with Copilot Studio?
It matches what Copilot Studio asks for, but Ryze AI has not run it there yet. The connector is a remote MCP server whose OAuth sign-in supports dynamic client registration, which is what Microsoft's Dynamic discovery option expects. It has not been run in Microsoft 365 Copilot either, so start with a copy of a file.
Can Copilot format a Google Doc?
No. Doc writes are plain text only, with no headings, links or formatting, and they either append at the end or replace the whole document.
Which transport does Copilot Studio support?
Streamable only. Microsoft's MCP guide for Copilot Studio says SSE is no longer supported after August 2025.
How much does it cost?
The connector is free to add, while the Drive tools need an active Ryze AI plan or trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year. Copilot Studio pricing is set by Microsoft.
How do I disconnect Google Drive from Copilot?
Delete the Ryze AI tool from the agent's Tools page in Copilot Studio, or switch it off with its Enabled toggle. To cut Ryze AI off from Drive, disconnect Google Drive under Integrations in Ryze AI or revoke the app in your Google account.