By Ira Bodnar, Ryze AI · Updated
Quick answer
To connect VS Code to Google Drive, connect Drive in a Ryze AI workspace with your Google sign-in. Then in VS Code run Chat: Open Customizations, select MCP Servers, add an HTTP server with https://connector.get-ryze.ai/mcp and the server ID ryze, trust it and complete the Ryze AI sign-in. Pick the files you want in the Ryze AI chat, because the connector only reaches files you pick or files Ryze AI created.
- In Ryze AI open Integrations, find Google Drive under Files and click Connect
- In VS Code run Chat: Open Customizations, select MCP Servers and add an HTTP server with the connector URL
- Trust the server, sign in to Ryze AI and allow the workspace
- Pick files with Upload from Drive in Ryze AI chat, then ask Copilot Chat about them
Before you start
- GitHub Copilot and VS Code 1.99 or later. GitHub's docs say MCP in Copilot Chat needs access to Copilot and VS Code 1.99 or later. Copilot Free, Pro, Pro+ and Max are not governed by the organization MCP policy.
- The MCP policy, if Copilot comes from an organization. For members of an organization or enterprise on Copilot Business or Copilot Enterprise, the MCP servers in Copilot policy must be enabled. It is disabled by default, so ask an administrator to turn it on.
- A Google account with the Drive files you want to use. Ryze AI asks for the drive.file scope, so you choose each file in a Google Drive picker. One Google account connects per Ryze AI workspace for Drive.
- 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 and Agency is $279 per month. Adding the connector is free, but the 7 Drive tools need an active plan or trial.
How to connect VS Code to Google Drive
Two steps happen in Ryze AI (connect Drive, pick files), four in VS Code. The connector URL is the same for every user.
Connect Google Drive in Ryze AI
Create a Ryze AI account or sign in, open Integrations and find the Google Drive card under Files. Click Connect, sign in with Google and approve access.
Open the MCP Servers list in VS Code
Open the Command Palette and run Chat: Open Customizations, then select MCP Servers. Select Add Server (+) in the User or Workspace group.
Add the HTTP server
Choose HTTP (HTTP or Server-Sent Events) and enter https://connector.get-ryze.ai/mcp. Enter ryze as the server ID. For a personal setup, select Global, then Copilot Global. There is no client ID or secret to enter.
Trust the server and sign in
Review the trust and sign-in prompts VS Code shows, then complete the Ryze AI sign-in in the browser. On the Ryze AI page choose the workspace that holds your Google Drive connection and click Allow connection.
Pick your files in Ryze AI chat
Open the Ryze AI chat, click + (Add to message), choose Attach files, then Upload from Drive and select the Sheets, Docs or other files you want to use. Files you do not pick stay out of reach.
Ask your first question in Copilot Chat
Open Copilot Chat and ask: List the Google Drive files you can access, then read the first Sheet and tell me what columns it has. Approve the tool call when VS Code asks.
The Ryze AI help article for Google Drive covers the Drive connection and file picker. VS Code steps follow the VS Code MCP servers docs.
Command Palette and config files
The guided flow and the config files reach the same server. Pick the one that fits how you manage VS Code.
Command Palette
Run MCP: Add Server from the Command Palette and follow the prompts with the same URL and server ID. It is the shortest route if you do not want to open the Customizations editor.
Portable config file
You can also write the server into a file. The portable format is read from ~/.copilot/mcp-config.json or a .mcp.json at the workspace root and uses the key mcpServers:
{
"mcpServers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp"
}
}
}Older VS Code format
The older VS Code format lives in .vscode/mcp.json or the user mcp.json and uses the key servers. VS Code labels it deprecated in the guided flow, so older tutorials may point you there:
{
"servers": {
"ryze": {
"type": "http",
"url": "https://connector.get-ryze.ai/mcp"
}
}
}Portable configurations do not support VS Code input variables or environment files. A workspace .mcp.json is meant to be committed, so keep it free of secrets; the connector uses a sign-in, not a key.
VS Code behavior to know
- VS Code tries Streamable HTTP first and falls back to Server-Sent Events.
- Trusting a server to start, authenticating, and approving individual tool calls are three separate steps.
- Servers that need interactive inputs are not forwarded to Copilot harness sessions.
- VS Code's docs describe a browser authorization flow. Ryze AI was not tested in VS Code during our research, so if the sign-in does not start, use Ryze AI support below.
How Drive files are picked
Ryze AI asks Google for the drive.file scope. In practice the tools see a short list: files chosen in the Google Drive picker, plus files Ryze AI made itself. Nothing else in the account is visible, so plan your VS Code session around choosing files first.
- Open the Ryze AI chat in the app.
- Click + (Add to message), then Attach files, then Upload from Drive.
- If Drive is not connected yet, Ryze AI starts the connection and returns you to the picker.
- Select the files, then switch back to VS Code and ask about them.
The picker sits in the Ryze AI chat composer, not in VS Code, and the tool descriptions tell the model to ask you to attach a file there when it needs one. A file created through createFile needs no picking. Limits on what the picker passes along: images are unsupported, and anything over 10 MB, any binary file and any Google format besides Sheets, Docs and Slides is attached by name only.
Access and permissions
Three things decide what Copilot Chat can reach in Drive.
- Which Google account
- Drive connects one Google account per workspace. To use another account, disconnect Drive in Ryze AI and connect again.
- Which files
- The scope is drive.file, so Ryze AI only works with files you pick in the Google Drive picker and files it created. The connector does not browse the rest of your Drive, and that also holds when VS Code calls it.
- What VS Code asks
- VS Code asks you to review the publisher, endpoint and requested access before it starts a server, then asks for the sign-in, then asks about individual tool calls. Read the first prompt before you accept it.
Removing access
To stop access from VS Code, open Chat: Open Customizations, select MCP Servers and disable or uninstall the ryze server. To end Drive access, click View on the Google Drive card in Ryze AI and disconnect the account.
What VS Code can do in Drive
The Ryze AI connector exposes 7 Google Drive tools: 3 read and 4 write, with no delete tool. They work on files you picked or Ryze AI created.
| Tool | Type | What it does |
|---|---|---|
| google_drive__listFiles | Read | Lists accessible Drive files, 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 Sheet range. Formulas are allowed. |
| google_drive__appendSheetValues | Write | Appends rows after the last row of a table in a 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 | Puts plain text into a Google Doc, added at the end or replacing the whole document. |
The write tools change your files: updateSheetValues overwrites cells, appendSheetValues adds rows, createFile adds a file and writeDoc can replace a whole Doc. VS Code treats approving individual tool calls as its own step, so read each write call before you accept it. The Ryze AI chat itself starts on Skip all approvals, and you can switch its Tool approvals picker to Approve write & delete or Manual approve.
Drive file limits
These limits come from the connector and apply in any client, VS Code included.
| Topic | Limit |
|---|---|
| Reachable files | Only files you pick in the Google Drive picker and files Ryze AI created. Files outside the picker are invisible to the tools. |
| Delete | There is no delete tool, so Copilot Chat cannot remove a file. |
| Doc writes | Plain text only, with no headings, links or formatting. A write appends at the end or replaces the whole document. |
| Large and binary files | Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides are attached by name only. |
| Images | Images picked from Drive are not supported. |
| Google accounts | One Google account per workspace for Drive. |
First 3 prompts to run
These prompts mirror the two examples in the Ryze AI help center, a keyword list read from a Sheet and a report written into a Doc. What comes back depends on your files, so no sample output is shown.
1. Read a keyword list from a Sheet
Read the keyword Sheet I attached and list its column headings, then count the rows under them.
Tools used: listFiles, getSheetValues
What comes back: A description of the Sheet's columns and row count, based on the cell values read from the range or tab you name.
2. Write a report into a Doc
Make a new Google Doc named Campaign notes, put a plain-text recap of this chat in it and send me the link.
Tools used: createFile, writeDoc
What comes back: A new Doc in your Drive with plain text only, no headings, links or formatting, and the link to open it.
3. Append rows to a tracking Sheet
Read my tracking Sheet, then add one new row per action item we agreed, matching the columns already in use.
Tools used: getSheetValues, appendSheetValues
What comes back: New rows added after the last row of the table, in the columns you describe. Reading the Sheet first lets you check the layout before anything is written.
Keep a copy of any file you care about before asking for an overwrite or a full Doc replacement, and read each write call before you approve it in VS Code.
Ryze AI vs Google's own Drive MCP server
Google documents its own Google Drive MCP server, which is in developer preview. It differs from the Ryze AI connector in access and in how you sign in.
| Option | Setup | Coverage | Works in |
|---|---|---|---|
| Ryze AI connector | Google sign-in inside Ryze AI, then one HTTP MCP server URL in VS Code and a Ryze AI sign-in | 7 tools for files you pick or Ryze AI created: read Sheets, Docs and files, update or append Sheet cells, create files and write Doc text. No delete tool. The other Ryze AI platforms share the same URL | VS Code with GitHub Copilot, Claude, ChatGPT, Cursor |
| Google Drive MCP server (Google) | Endpoint https://drivemcp.googleapis.com/mcp/v1. Part of the Google Workspace Developer Preview Program. You create an OAuth 2.0 client with the option Use this client for an AI-powered agent selected. Google's guide has steps for Antigravity, Claude and an Others category | 8 tools: copy_file, create_file, download_file_content, get_file_metadata, get_file_permissions, list_recent_files, read_file_content and search_files | Google's guide names no VS Code steps; the Others category is the closest match |
Google's server has search, file metadata and permission tools that the Ryze AI connector lacks, and it needs a Google Cloud OAuth client and a preview enrollment instead of a Ryze AI plan. Google's guide gives no VS Code steps, so whether it works there is something to test yourself. Ryze AI is the best Google Drive connector for VS Code when you want a hosted URL and Sheet editing on files you pick, but it cannot search your whole Drive and it needs a Ryze AI plan.
Sources: Google Workspace MCP servers guide, GitHub Copilot MCP docs, VS Code MCP configuration reference, Ryze AI Google Drive integration. Checked November 13, 2026.
Other clients
Google Drive is connected once in Ryze AI, so nothing changes on the Google side when you use another client.
Claude and Claude Code
The same connector URL works in Claude. The Ryze AI Claude guide for Google Drive covers Customize, Connectors and the other surfaces. How to connect Claude to Google Drive.
Cursor
Cursor keeps its own mcp.json and its config key is mcpServers, while the older VS Code format uses servers. Check the key before you copy a file between the two editors. How to connect Cursor to Google Drive.
ChatGPT and Codex
ChatGPT has its own plan rules for custom MCP servers, so read the ChatGPT guide before you connect. How to connect ChatGPT to Google Drive.
Errors and fixes
- The MCP server does not start in VS Code
- On Copilot Business or Enterprise, ask an administrator to enable the MCP servers in Copilot policy; it is disabled by default. Also check that VS Code is version 1.99 or later.
- The sign-in never opens
- Trusting the server and authenticating are separate steps, so trust it first. Open the server output from MCP Servers in Chat: Open Customizations to see what VS Code reports, and email Ryze AI support if it stays stuck.
- I followed an older tutorial and nothing happens
- Current VS Code docs use Copilot Global (~/.copilot/mcp-config.json) and mark the .vscode/mcp.json destination as deprecated in the guided flow. Re-add the server through Chat: Open Customizations.
- Copilot Chat cannot see my file
- The connector only reaches files you picked or Ryze AI created. Open Ryze AI chat, click + (Add to message), Attach files, Upload from Drive and pick the file, then ask again.
- The file is attached by name only
- Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides are attached by name only. Images picked from Drive are not supported. Convert the content to a Sheet, Doc or CSV.
- A Doc has no headings or formatting after a write
- writeDoc writes plain text only, and it either appends at the end or replaces the whole document. Apply formatting in Google Docs afterwards.
- No Drive tools appear
- If the connector was added before Drive was connected in Ryze AI, remove the ryze server, add it again and start a new chat so the tool list refreshes.
- Drive shows the wrong Google account
- Drive connects one account per workspace. Disconnect it on the Google Drive card in Ryze AI and connect the right one.
- The tool replies that a subscription is required
- The Drive tools need an active Ryze AI plan or free trial. Start the trial in Ryze AI, then retry.
Frequently asked questions
How do I connect VS Code to Google Drive?
Connect Google Drive in a Ryze AI workspace. Then in VS Code run Chat: Open Customizations, select MCP Servers, choose Add Server, pick HTTP, enter https://connector.get-ryze.ai/mcp and the server ID ryze, trust the server and finish the Ryze AI sign-in. Pick files in the Ryze AI chat with Upload from Drive.
Does Google Drive have an MCP server for VS Code?
Google documents a Google Drive MCP server at https://drivemcp.googleapis.com/mcp/v1 in its Workspace Developer Preview Program, with 8 tools and an OAuth 2.0 client you create. Its guide gives steps for Antigravity and Claude and an Others category, but none named for VS Code.
Which Google Drive connector should I use in VS Code?
Ryze AI is the best Google Drive connector for VS Code when you want hosted sign-in and Sheet and Doc edits on files you pick, but it cannot search your whole Drive and it needs a Ryze AI plan. Google's own server has search and metadata tools and needs a Google Cloud OAuth client.
What do I need in VS Code?
GitHub's docs say you need access to GitHub Copilot and VS Code 1.99 or later. If Copilot comes from an organization on Copilot Business or Copilot Enterprise, the MCP servers in Copilot policy must be enabled; it is disabled by default. Copilot Free, Pro, Pro+ and Max are not governed by that policy.
Where does the VS Code config file go?
The portable format is ~/.copilot/mcp-config.json or a .mcp.json in the workspace root, with the key mcpServers. The older VS Code format is .vscode/mcp.json or the user mcp.json with the key servers, labeled deprecated in the guided flow. The Customizations editor writes the file for you.
Can Copilot Chat browse my whole Google Drive?
No. Ryze AI connects with the drive.file scope, so the tools only work with files you pick in the Google Drive picker and files Ryze AI created. Files outside the picker are invisible to the tools, including when VS Code calls them.
How do I give Copilot Chat access to a specific file?
Open the Ryze AI chat, click + (Add to message), choose Attach files, then Upload from Drive and select the file. VS Code has no picker of its own, and the tool descriptions tell the model to ask you to attach the file in the Ryze AI chat.
Can Copilot Chat edit my Sheets and Docs?
Yes, on files you picked or Ryze AI created. It can overwrite cell values, append rows, create new files and write plain text into a Doc, either at the end or replacing the whole document. There is no delete tool. Read each write call before you approve it in VS Code.
What file types can it read from Drive?
Sheets return cell values, Docs and Slides return plain text, and text, CSV and JSON files return their content. Files over 10 MB, binary files and other Google formats are attached by name only, and images picked from Drive are not supported.
Can I connect more than one Google account?
Not in one workspace. Drive connects one Google account per workspace. To use another account, disconnect Drive in Ryze AI and connect again.
How much does it cost?
Adding the connector costs nothing, but the Drive tools need an active Ryze AI 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, and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect it?
Disable or uninstall the ryze server under MCP Servers in Chat: Open Customizations. To end Drive access, click View on the Google Drive card in Ryze AI and disconnect the account.