By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect OpenClaw to Google Drive is the Ryze AI connector. Connect Google Drive in a Ryze AI workspace, then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth. Use openclaw mcp set while the Gateway is stopped, or Add server under Settings > MCP in the Control UI. Sign in with openclaw mcp login ryze. OpenClaw then lists 7 Drive tools, 3 that read and 4 that write. They reach only the files you pick in the Ryze AI chat and the files Ryze AI creates, because the Google sign-in uses the drive.file scope.
- In Ryze AI open Integrations, find Google Drive under Files, click Connect and approve the Google sign-in
- In a Ryze AI chat pick the files to share with + > Attach files > Upload from Drive
- Stop the Gateway with openclaw gateway stop and run openclaw mcp set ryze with the connector URL, or add it under Settings > MCP while the Gateway runs
- Run openclaw mcp login ryze, click Allow connection on the Ryze AI page, then start the Gateway again
OpenClaw to Google Drive at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in OpenClaw as one remote MCP server named ryze |
| Server address | https://connector.get-ryze.ai/mcp, with transport set to streamable-http |
| Sign-in | OAuth. Run openclaw mcp login ryze while the Gateway is stopped, or have an administrator click Sign in under Settings > MCP. A Ryze AI API key in a bearer header is the other route |
| Drive tools | 7 in all: 3 that read (listFiles, readFile, getSheetValues) and 4 that write (updateSheetValues, appendSheetValues, createFile, writeDoc) |
| Can it change files | Yes. It can overwrite Sheet cells, append rows, create files and write text into Docs. There is no delete tool |
| Which files it reaches | Only files picked in the Ryze AI chat and files Ryze AI created. It does not browse or search the whole Drive |
| Other data in the same chat | Any other platform connected in the same Ryze AI workspace is served from the same URL |
| OpenClaw plan | None to buy. OpenClaw is MIT licensed and self-hosted, and its docs say there is no paid tier |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. SEO Starter is $129 per month with a 3-day free trial. Connecting is free; the tools need an active plan or trial |
| Google's own option for OpenClaw | A Drive MCP server in Developer Preview at https://drivemcp.googleapis.com/mcp/v1. Google's setup page names Antigravity and Claude plus a generic section for other clients, and does not name OpenClaw |
| Last tested | 8 Drive calls through the connector from Claude Code on November 14, 2026, none of them on a real file. No step was run inside OpenClaw |
Before you start
- OpenClaw. It is an open-source project under the MIT license that you host yourself, and its docs say it has no paid tier. You need a running Gateway plus one of these: the openclaw command on the Gateway machine, administrator access to the Control UI, or write access to the Gateway's openclaw.json.
- A Google account that holds the files. Ryze AI signs in with Google OAuth and the drive.file scope. Only files you choose in the Google Drive picker, and files Ryze AI creates, can be reached.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and SEO Starter is $129 per month with a 3-day free trial. Adding the connector is free; the Drive tools need an active plan or trial.
- One Google account per workspace. Drive connects a single Google account in each Ryze AI workspace. To use another account, disconnect Drive and connect it again.
- A note on testing. Ryze AI has no help-center page for OpenClaw and has not tested the connector there. The OpenClaw steps follow OpenClaw's own documentation for remote servers that use OAuth, as it read on November 15, 2026.
How to connect OpenClaw to Google Drive
Connecting Drive happens in Ryze AI, picking files happens in the Ryze AI chat, and the rest happens in OpenClaw. 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. You can also start from a Ryze AI chat: + (Add to message) > Attach files > Upload from Drive. If Drive is not connected yet, Ryze AI starts the connection and returns you to the file picker.
Pick the files to share
In a Ryze AI chat choose + > Attach files > Upload from Drive and select the Sheets, Docs or other files you want OpenClaw to work with. With the drive.file scope the tools see only these files and files Ryze AI created. OpenClaw has no Drive picker of its own, so this step stays in the Ryze AI chat.
Register the connector in OpenClaw
Stop the Gateway first with openclaw gateway stop: since OpenClaw 2026.10.10 (November 3, 2026) the CLI refuses to change saved servers while a Gateway owns the state directory. Then run: openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'. This stores a server named ryze. The same entry can go under mcp.servers in ~/.openclaw/openclaw.json, or be added with Add server under Settings > MCP in the Control UI while the Gateway keeps running.
openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryzeSign in from the OpenClaw CLI
With the Gateway still stopped, run: openclaw mcp login ryze. A browser opens on the Ryze AI page. Sign in if asked, choose the workspace that holds your Google Drive connection and click Allow connection, then start the Gateway again. An administrator can skip the stop and click Sign in for the ryze server under Settings > MCP instead.
Finish the sign-in on a remote machine if needed
If the browser runs on a different machine from OpenClaw, approve the sign-in there and hand the code it returns to the CLI with the --code option of openclaw mcp login. If the callback address also carries an iss value, pass that value with --issuer.
Ask your first question
Once credentials exist, OpenClaw includes the server in the agent runtime. If you added the connector before Drive was connected, remove it and add it again so the tool list refreshes. Then ask: List the Drive files you can reach, newest first.
The Ryze AI help center article for Google Drive covers the Google side of the connection. OpenClaw's own pages on the MCP registry commands and transports and OAuth cover the OpenClaw side.
Sources: OpenClaw: connect MCP servers, OpenClaw MCP registry commands, OpenClaw transports and OAuth (checked November 15, 2026).
CLI, Control UI, openclaw.json and API key
OpenClaw CLI
openclaw gateway stop
openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login ryzeset writes the server definition and login runs the OAuth flow, keeping the credentials on the Gateway host. Start the Gateway again afterwards. The flag form is openclaw mcp add ryze --url https://connector.get-ryze.ai/mcp --transport streamable-http --auth oauth. The read-only commands openclaw mcp show ryze, list and status print what is saved.
Control UI: Settings > MCP
Open the MCP page of the Control UI (/settings/mcp, with /mcp kept as an alias), pick Add server under Configured servers, name it ryze, choose Streamable HTTP and paste the URL. OpenClaw's docs place OAuth settings in the scoped config editor lower on that page, so set auth: "oauth" there and click Sign in. The route needs administrator access, and Sign in works only when the Control UI is opened on the Gateway's loopback address, its own HTTPS address or its published Tailscale address. In a chat, + > Plugins > Add MCP server saves a server for This session or Everywhere.
openclaw.json
{
mcp: {
servers: {
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
},
},
},
}Edit ~/.openclaw/openclaw.json. It is JSON5, so comments and trailing commas are allowed. The Gateway watches the file and applies edits, and a key it does not recognize stops it from starting, so keep the entry under mcp.servers. Sign in afterwards with openclaw mcp login ryze on a stopped Gateway, or with Sign in under Settings > MCP.
A Ryze AI API key instead of OAuth
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
headers: { Authorization: "Bearer ${RYZE_API_KEY}" },
}Drop auth: "oauth" and send the key as a bearer header, because OpenClaw ignores static Authorization headers while auth: "oauth" is on. Keep the key in an environment variable. A ${RYZE_API_KEY} reference does not trigger the literal-value warning of openclaw doctor when the variable is set.
Transport and timeouts
A remote entry takes the transport streamable-http or sse, and OpenClaw reads a URL entry with no transport as sse, so set streamable-http for this address. A request times out after 60 seconds by default, and the tool list at session start gets 10 seconds when requestTimeoutMs is not set. A large Sheet read that runs long needs a bigger requestTimeoutMs on the entry.
OpenClaw and MCP: the facts in one table
| Question | Answer from OpenClaw's docs |
|---|---|
| Where a server is added | Settings > MCP > Add server in the Control UI, + > Plugins > Add MCP server in a chat, openclaw mcp add or set in a terminal, or mcp.servers in ~/.openclaw/openclaw.json |
| Config file | ~/.openclaw/openclaw.json in JSON5. Edits apply without a restart; an unknown key blocks startup |
| Transports | stdio for local commands, plus SSE and Streamable HTTP for addresses. type: "http" is rewritten to transport: "streamable-http" by openclaw mcp set and openclaw doctor --fix |
| Sign-in | auth: "oauth" on an HTTP entry, then openclaw mcp login with the Gateway stopped, or Sign in under Settings > MCP for an administrator |
| Whose account | One shared credential that the operator manages, by default. oauth.identity: "per-requester" gives each sender their own sign-in and needs gateway.publicOrigin set to the Gateway's HTTPS origin |
| Approval | MCP tools follow the tool profiles and tool policy of other tools. The coding and messaging profiles include them, minimal hides them, and tools.deny: ["bundle-mcp"] switches them off. Per-call prompts are documented for Codex runs only |
| Tool names | The agent sees <server>__<tool>. openclaw mcp doctor ryze --probe opens a live connection and lists the tools |
| Plan | No paid tier; MIT licensed and self-hosted |
| Where servers are managed | The Control UI MCP page, or openclaw mcp list, show, status, doctor, probe, tools, logout and unset |
| Admin controls | Adding a server from a chat and signing in from Settings need administrator access. enabled: false keeps an entry but hides its tools |
Sources: OpenClaw: connect MCP servers, MCP registry commands, transports and OAuth, MCP config, Gateway configuration, MCP in the Control UI, Control UI chat, OpenClaw docs home (checked November 15, 2026).
Other clients
The same URL works in other MCP clients. Google Drive is connected once in Ryze AI, so nothing changes on the Google side.
Claude Code
Claude Code registers the same URL with one claude mcp add command.
ChatGPT and Claude
Both add the URL as a custom connector, with plan limits that differ from OpenClaw's.
Permissions and access
Four things decide what OpenClaw can reach in Drive.
- Which Google account
- One Google account per Ryze AI workspace. Ryze AI signs in with Google OAuth on that account.
- Only picked files
- The drive.file scope limits access to files you choose in the picker and files Ryze AI created. A file outside those two groups looks the same as a missing file.
- Whole file, not one tab
- Google applies its Sheets scopes to a spreadsheet file and cannot limit them to a single tab, so a picked Sheet is reachable on every tab.
- Shared sign-in
- By default OpenClaw's OAuth credential is shared and operator-managed, so everyone who talks to that agent works with the one Ryze AI sign-in and the same picked files. Per-requester sign-in needs oauth.identity set to per-requester and gateway.publicOrigin set to an HTTPS origin.
What the connection is allowed to do
Two sign-ins stand between OpenClaw and your files. OpenClaw signs in to the Ryze AI connector, and Ryze AI holds a Google sign-in for Drive. The rows show what each grants and where the fact was found.
| Part | What it grants | Found in |
|---|---|---|
| OpenClaw to the connector | An OAuth sign-in with PKCE (S256) and the authorization code and refresh token grants. The connector offers two scopes, mcp:read and mcp:write | Ryze AI connector test, November 13, 2026 |
| The saved credential | One shared, operator-managed sign-in per server unless per-requester OAuth is on, kept in the Gateway's openclaw.sqlite | OpenClaw transports and OAuth page, November 15, 2026 |
| Ryze AI to Google | Google OAuth on your Google account with the drive.file scope. No API key, no service account | Ryze AI facts and Google Drive API scopes page, November 14, 2026 |
| What drive.file means | Google describes it as letting users choose which files to share with an app, and it lists the scope as non-sensitive. It works with all Drive API REST resources | Google Drive API scopes page, November 14, 2026 |
| Roles in Drive | No roles are assigned. The sign-in is a user consent, so the files are those of the signed-in Google user that were picked or created | Google Drive API scopes page, November 14, 2026 |
| Plan | The tools need an active Ryze AI plan or trial | Ryze AI facts |
Not included: the broad scopes drive, drive.readonly and drive.metadata.readonly (all Restricted by Google), and the spreadsheets and documents scopes (Sensitive). That is why there is no Drive-wide search, no images or PDFs, no file move or share, no delete tool, and no second Google account in the same workspace. Google's own Drive MCP server asks for drive.readonly as well as drive.file, so it can read every file you can open. The Ryze AI connection holds drive.file only.
Sources: Drive API scopes, Sheets API scopes, Google Picker overview (checked November 14, 2026).
Removing access
To cut OpenClaw off, stop the Gateway and run openclaw mcp logout ryze, which deletes the saved credentials but keeps the entry, or openclaw mcp unset ryze, which removes the entry. enabled: false on the entry hides its tools without deleting anything. To end the Google access itself, disconnect Google Drive under Integrations in Ryze AI.
What OpenClaw can do in Drive
The Ryze AI connector exposes 7 Google Drive tools: 3 read and 4 write. There is no delete tool.
| Tool | Type | What it does |
|---|---|---|
| google_drive__listFiles | Read | Lists the Drive files the app can access, newest first, with an optional Drive search filter. |
| google_drive__readFile | Read | Reads a 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 | Writes plain text into a Google Doc, appended at the end or replacing the whole document. |
Keeping the write tools in check
OpenClaw documents per-call approval prompts for Codex runs only. In its built-in runtime, MCP tools follow the same tool profiles and policy as other tools, and inside a chat, + > Plugins > Tool access lets you deny single tools for that session. The four write tools overwrite or add content, so a toolFilter with an exclude list on the server entry is the standing way to keep them from the agent. Entries take exact names or simple * globs; run openclaw mcp doctor ryze --probe first to see the names OpenClaw reports. In the Ryze AI chat itself, the Tool approvals picker starts on Skip all approvals, and Approve write & delete or Manual approve can be chosen.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
toolFilter: {
exclude: [
"*updateSheetValues", "*appendSheetValues",
"*createFile", "*writeDoc",
],
},
}Limits in numbers
| Limit | Figure | Set by |
|---|---|---|
| File size for reads | Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides come back by name only, with content: null | Ryze AI tool definition and facts |
| Input lengths | File, spreadsheet and document IDs 1 to 200 characters. Range 1 to 300. Drive search filter 1 to 500. New file name up to 300 and content up to 200,000 characters. writeDoc content 1 to 200,000 | Ryze AI tool definitions, with the 200, 500 and minimum 1 also returned by test calls |
| Doc writes | Plain text only, appended or replacing the whole document | Ryze AI facts |
| Drive API quota | 1,000,000 quota units per minute per project and 325,000 per minute per user per project, for Cloud projects created on or after May 1, 2026. Which quota set applies to the project behind the Ryze AI connection was not checked | |
| Sheets API requests | 300 read and 300 write requests per minute per project, 60 of each per minute per user per project. Over the quota returns 429 | |
| Docs API requests | Read 3,000 per minute per project and 300 per user. Write 600 per minute per project and 60 per user | |
| Over the Drive quota | 403 User rate limit exceeded, and the backend may answer 429. Google advises truncated exponential backoff | |
| File sizes in Drive | Documents up to 1.02 million characters, spreadsheets up to 20 million cells, other files up to 5 TB | Google Drive Help |
| Trash | Files moved to the Trash are deleted forever after 30 days | Google Drive Help |
| OpenClaw request time | 60 seconds per request, and 10 seconds for the tool list at session start unless requestTimeoutMs is set | OpenClaw |
The Google rows bind any app calling the Drive, Sheets or Docs APIs. None of the test answers carried a quota or rate figure, so this guide cannot say which Google quota the Ryze AI connection draws on.
Sources: Drive API limits, Sheets API limits, Docs API limits, Drive file sizes, Drive trash (checked November 14, 2026); OpenClaw MCP config, OpenClaw: connect MCP servers (checked November 15, 2026).
Drive calls through the connector, tested
These are the 8 Drive calls sent through the Ryze AI connector on November 14, 2026, from a Claude Code session and not from OpenClaw. Each was built so that no real file could come back: a name filter that matches nothing, IDs that do not exist, a field that does not exist, a page token that does not exist, and values that are too long or too short.
| Call | Tool | Result |
|---|---|---|
| Name filter that matches nothing | listFiles | Worked. An empty list, {"files":[]}, with no error and no paging token |
| File ID that does not exist | readFile | Answered not_found with a File not found message |
| Spreadsheet ID that does not exist, range Sheet1!A1:B2 | getSheetValues | Answered not_found |
| Filter on a field that does not exist | listFiles | Error 400, Invalid Value, location q |
| Page token that does not exist | listFiles | Error 400, Invalid Value, location pageToken |
| File ID of 201 characters | readFile | Refused by the connector: invalid_arguments, maximum 200 |
| Filter of 501 characters | listFiles | Refused by the connector: invalid_arguments, maximum 500 |
| Empty range | getSheetValues | Refused by the connector: invalid_arguments, minimum 1 |
The tool list also loaded, with all 7 definitions. No answer carried a quota, rate-limit or cost figure, and no real file, Sheet value or Doc text came back.
First 3 prompts to run
Each answer comes from your own files, so this page describes what comes back instead of showing sample output.
1. Read a keyword list from a Sheet
Read the Keywords tab of the Sheet I attached in Ryze AI and list the first 20 rows.
Tools used: google_drive__getSheetValues
What comes back: The cell values of that tab or range. Only a Sheet you picked or one Ryze AI created can be read, and the whole file is reachable, not one tab.
2. See which files are reachable
List the Drive files you can reach, newest first.
Tools used: google_drive__listFiles
What comes back: The picked files and the files Ryze AI created, newest first. An empty list means nothing was picked yet, not that Drive is empty.
3. Write a report into a new Doc
Create a Google Doc called Weekly notes and write this summary into it as plain text.
Tools used: google_drive__createFile, google_drive__writeDoc
What comes back: A link to the new Doc. The text arrives without headings, links or formatting, since Doc writes are plain text.
To change an existing Sheet, ask in plain words, for example to append this week's rows to the log Sheet. Check the range first: updateSheetValues replaces the cells in the range you give it, and appendSheetValues adds rows after the last row of the table.
10 jobs to hand to OpenClaw
Ten jobs to give an OpenClaw agent, each matched to the tool behind it. The default connection means the standard Google sign-in with the drive.file scope. None of these jobs was run on a real file for this guide.
| Job | What to ask OpenClaw | Tool | Default connection |
|---|---|---|---|
| Keyword list from a Sheet | Read the Keywords tab of the Sheet I picked. | getSheetValues | Yes |
| Reachable files | List the files you can reach, newest first. | listFiles | Yes, picked and Ryze AI created files only |
| Brief from a Doc | Read the brief Doc and give me its main points. | readFile | Yes, as plain text |
| Slides text | Pull the text from the picked deck and summarize it. | readFile | Yes, plain text only |
| CSV or JSON export | Read the CSV I picked and describe its columns. | readFile | Yes, up to 10 MB |
| Report into a new Doc | Create a Doc and write this report into it. | createFile, then writeDoc | Yes, plain text only |
| Log rows | Append this week's rows to the log Sheet. | appendSheetValues | Yes, after the last row of the table |
| Overwrite a range | Replace the cells in B2:D10 with these values. | updateSheetValues | Yes. Existing cells in the range are replaced |
| New Sheet with a table | Create a Sheet and fill it with this table. | createFile, then updateSheetValues | Yes. The Sheet is created empty and filled in a second call |
| Save a result as a file | Save this output as a CSV in Drive. | createFile | Yes, content inline up to 200,000 characters |
Five jobs have no tool: deleting or trashing a file, searching or browsing the whole Drive, reading an image or a PDF, formatting a Doc or editing one section in place, and using two Google accounts in one workspace.
5 ways to connect OpenClaw to Google Drive
Google, Zapier and Composio each offer a route into Drive that suits OpenClaw's remote-server support, and Google's Workspace CLI names OpenClaw directly. None of them was set up inside OpenClaw for this guide. This guide treats the first, the Ryze AI connector, as the main way: the Google side is one sign-in inside Ryze AI with no Google Cloud project of your own, and the OpenClaw side is one remote entry. Every other page below was read on November 14, 2026, and nothing from them was installed.
| Way | Runs where | Setup for OpenClaw | What it reaches in Drive | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | A streamable-http entry named ryze with auth oauth, from Settings > MCP, openclaw mcp set or openclaw.json, then one sign-in. A Ryze AI API key in a bearer header can stand in for the sign-in | 7 tools on files you pick and files Ryze AI creates: list, read, read and write Sheet cells, create files, write Docs | Paid Ads $89 per month with a 7-day free trial, or SEO Starter $129 per month with a 3-day free trial |
| Google's Drive MCP server | Hosted by Google at https://drivemcp.googleapis.com/mcp/v1, Streamable HTTP with OAuth 2.0 | Join the Google Workspace Developer Preview Program, enable the Drive API and the Drive MCP API in a Google Cloud project, add the scopes drive.readonly and drive.file, and create a Web application OAuth client marked 'Use this client for an AI-powered agent'. Which OpenClaw setting takes that client ID and secret was not confirmed | 8 tools: search, file content and metadata, permissions, recent files, download, create and copy. It sees every file you can open, minus files that fail Google's eligibility checks. No delete, move, rename or share tool | No separate price stated. Developer Preview, and a Google Cloud project is required |
| Zapier MCP | Hosted by Zapier | Zapier's quickstart lists OpenClaw among its MCP clients. Generate your Zapier MCP address, choose the Drive actions, then save the address in OpenClaw as a Streamable HTTP server | The Google Drive actions you switch on in Zapier. The page shows 8 before its Load More button, including Copy File, Delete File (Permanent), Upload File, Create Folder and Create File From Text, and states no total | Each successful tool call uses 2 tasks of your Zapier plan; failed calls do not count |
| Composio | Hosted by Composio at https://connect.composio.dev/mcp | Composio's Google Drive page lists OpenClaw among the assistants that work with it. Its setup steps are written for ChatGPT and Cursor, and no OpenClaw steps were found. The address is a Streamable HTTP server | 92 tools and 7 triggers listed for Google Drive, with a managed Google OAuth app so you sign in with your normal account | Pricing page: free plan at $0 with 10,000 tool calls per month, Standard at $18 per seat per month. Another Composio page gives a different free allowance, so check the pricing page |
| Google Workspace CLI (gws) | On your computer, a command-line tool | Install with npm install -g @googleworkspace/cli, then gws auth setup and gws auth login. Its README names OpenClaw among the agents it lists and ships agent skills. It is a CLI and skills route, and the README does not mention MCP | Every Workspace API method Google's Discovery Service lists, limited by the scopes chosen at login | Free, Apache License 2.0. The README says it is not an officially supported Google product |
Options that do not fit this setup
- The Google Workspace app in Gemini. It reads Drive files inside Gemini and names no other assistant. Google's help page says it cannot create folders or move content in Drive.
- The Google Workspace extension for Gemini CLI. It adds Drive, Sheets, Docs and Slides tools to Gemini CLI only, and includes trash and rename in Drive.
- The Google Drive app in ChatGPT and the Google Drive connector in Claude. Each works inside its own assistant. OpenAI's article names no plan, and Anthropic's says the connectors are available for all users.
- taylorwilsdon/google_workspace_mcp. An open-source Python server you run yourself, with 120+ tools across twelve Workspace services, an MIT license and 3,516 GitHub stars on November 14, 2026. It needs your own Google OAuth client. Its README names Claude, Claude Code, ChatGPT, Codex, VS Code, LM Studio and Open WebUI, and not OpenClaw, although it offers stdio and Streamable HTTP, both of which OpenClaw supports.
- @modelcontextprotocol/server-gdrive. The old reference Drive server. Its last version, 2025.1.14, is marked deprecated on npm, and its repository was archived on May 29, 2025.
- A Ryze AI plugin in ClawHub. ClawHub, OpenClaw's public registry for skills and plugins, had no Ryze AI plugin on November 15, 2026, so the connector is added by its address.
Which one to pick
Ryze AI is the best Google Drive connector for OpenClaw when the job is reading and writing a few picked Sheets and Docs from one hosted URL, but it only reaches files you pick or Ryze AI created, has no delete tool, writes Docs as plain text and needs a Ryze AI plan. Google's own server fits a team that wants to search every file it can open and is willing to join a Developer Preview, run a Google Cloud project and register an OAuth client. Zapier suits a team that already pays for Zapier tasks and wants actions such as moving or permanently deleting files, which the Ryze AI connector lacks. Composio lists the most tools, 92, behind its own managed sign-in. The Workspace CLI gives a developer scripted access to the whole API. None of the four was installed for this guide, so try one on a test file before it touches work that matters.
Sources: Google Drive MCP server setup, Drive MCP reference, Drive MCP file eligibility, Zapier Google Drive MCP, Zapier MCP quickstart, Composio Google Drive toolkit, Composio pricing, Google Workspace CLI, Gemini Workspace app help, Gemini CLI Workspace extension, OpenAI Google Drive app, Claude Google Workspace connectors, google_workspace_mcp, server-gdrive on npm (checked November 14, 2026); ClawHub, OpenClaw MCP transports, OpenClaw on GitHub (checked November 15, 2026).
Google Drive and OpenClaw: dates that matter
| Date | What happened |
|---|---|
| November 19, 2024 | The reference Google Drive MCP server, @modelcontextprotocol/server-gdrive, first appeared on npm. Its last version came on January 14, 2025 and carries a deprecation notice. |
| January 30, 2026 | OpenClaw 2026.1.29 renamed the npm package and the CLI to openclaw. |
| March 31, 2026 | OpenClaw 2026.3.31 added remote HTTP and SSE servers by URL under mcp.servers, with auth headers and an optional streamable-http transport. |
| April 22, 2026 | Google's release notes put the Drive MCP server in Developer Preview. A copy_file tool followed on May 21, 2026. |
| May 1, 2026 | Drive API quotas moved from request counts to quota units for Cloud projects created on or after this date. |
| July 13, 2026 | Google's MCP servers for Docs, Sheets and Slides arrived in Developer Preview. |
| August 31, 2026 | OpenClaw 2026.8.1, also called OpenClaw 2.0, added servers from the chat composer and per-requester OAuth for shared servers. |
| September 23, 2026 | OpenClaw 2026.9.6 let administrators sign in to MCP connectors from Settings. |
| October 1, 2026 | Google's Docs, Sheets and Slides MCP servers gained comment reading and management. |
| November 3, 2026 | OpenClaw 2026.10.10 began protecting MCP configuration while the Gateway runs. The commands openclaw mcp set and login now need the Gateway stopped. |
| November 10, 2026 | OpenClaw 2026.11.3 came out. On November 15, 2026 it was the newest stable release, and its notes list no MCP change. |
| November 11, 2026 | Google's Workspace MCP servers began rejecting requests from OAuth clients not marked as agentic. Apps that only call the Workspace REST APIs are not affected. |
Sources: Google Workspace release notes, Drive API limits, archived reference servers, server-gdrive on npm (checked November 14, 2026); OpenClaw releases, changelog 2026.3.31, changelog 2026.8.1, release 2026.9.6, release 2026.10.10 (checked November 15, 2026).
How this guide was tested
Three dates stand behind this guide. The connector's sign-in answer was checked on November 13, 2026, the Drive tools were called on November 14, 2026, and the OpenClaw steps were compared with OpenClaw's documentation on November 15, 2026. Nothing was run inside OpenClaw.
| What was run | What came back |
|---|---|
| The connector address without a sign-in, November 13, 2026 | HTTP 401. OpenClaw's docs say a 401 at startup is logged as authentication refused (401); that line was not seen, because OpenClaw was not run. |
| The tool list in a signed-in Claude Code session, November 14, 2026 | All 7 Drive tools, 3 read and 4 write, and no other google_drive tool. |
| One list call with a filter that matches nothing, November 14, 2026 | Worked, and returned an empty list. |
| Seven calls built to fail, November 14, 2026 | All seven were refused or answered not found: two not_found answers, two Error 400 answers and three argument errors. The messages are in the errors table below. |
| A read of every answer for quota and cost figures, November 14, 2026 | None of the answers carried a quota, rate-limit or cost figure. |
Not run for this page: every step inside OpenClaw. No Gateway was installed or started, no server was saved and no sign-in was tried, so openclaw mcp set, openclaw mcp login, Settings > MCP and the openclaw.json entry follow OpenClaw's documentation as it read on November 15, 2026. The tool calls came from Claude Code, which reaches the same connector. No real file was listed or read, and none of the 4 write tools was called, because they change files. Google's, Zapier's and Composio's pages were read and nothing was installed.
Errors and fixes
Exact messages from the connector test
The connector sent back these seven messages on November 14, 2026, copied word for word. Argument errors begin with Invalid arguments for and the tool name, such as google_drive.readFile; the table shows the part after that. If one turns up in an OpenClaw chat or log, this is what it means.
| Message | Meaning | What to do in OpenClaw |
|---|---|---|
| File not found: <redacted>. | The file ID does not exist, or the file was not picked in the Ryze AI Drive picker and was not created by Ryze AI. With drive.file, a file outside those two groups looks like a missing one. | Attach the file with Attach files > Upload from Drive in a Ryze AI chat, then ask again. |
| Requested entity was not found. | The spreadsheet ID does not exist, or the Sheet is not one the connection can reach. | Pick the Sheet in the Ryze AI Drive picker, or ask for the file list to get the ID of a Sheet the connection can reach. |
| Invalid Value (location: q) | The search filter is not valid Drive query syntax, here a field name that does not exist. | Use a term such as name contains 'KPI', or leave the filter out. |
| Invalid Value (location: pageToken) | The page token did not come from an earlier list call. The message is the same as for a bad filter; only the location differs. | Start the list again without a page token. |
| Too big: expected string to have <=200 characters | The file ID was longer than the 200 characters the tool accepts. This usually means a whole link or extra text was passed as the ID. | Pass only the ID part of the file link. |
| Too big: expected string to have <=500 characters | The search filter was longer than 500 characters. | Shorten the filter to one name contains term. |
| Too small: expected string to have >=1 characters | The range was empty. getSheetValues needs a tab name or an A1 range. | Pass a tab name such as Sheet1, or a range such as Sheet1!A1:D50. |
Other problems
- The Drive tools do not appear in OpenClaw
- Until shared credentials exist, OpenClaw leaves the server out of the agent runtime instead of failing the turn. Run openclaw mcp login ryze with the Gateway stopped, then check with openclaw mcp status or openclaw mcp doctor ryze --probe. If you added the connector before Drive was connected in Ryze AI, remove the entry and add it again so the tool list refreshes.
- The server connects but the tool list is empty or times out
- The tool list at session start gets 10 seconds when requestTimeoutMs is not set. Raise requestTimeoutMs on the entry, and confirm transport is streamable-http, because OpenClaw reads a missing transport as sse.
- The sign-in page opens on the wrong machine
- Approve it in the browser, then give the code it returns to openclaw mcp login ryze with --code, and the iss value with --issuer if the callback carries one.
- The API key is ignored
- Static Authorization headers are ignored while auth: "oauth" is on. Remove auth for the key route, or remove the header and use OAuth.
- An openclaw mcp command refuses to run
- Since OpenClaw 2026.10.10 (November 3, 2026), the commands that change saved servers, and login, refuse while a Gateway owns the state directory. Stop the Gateway, run the command and start it again. To skip the stop, edit openclaw.json, which the Gateway watches, or use Settings > MCP.
- The log says authentication refused (401)
- OpenClaw's docs use this line when a Streamable HTTP server rejects startup with HTTP 401, which is how the Ryze AI connector answers before you sign in. Finish the sign-in. The pairing comes from the docs and was not seen in a run.
- Status shows authorization-required, or the token is rejected with insufficient_scope
- Run openclaw mcp login ryze again with the Gateway stopped.
- The Gateway will not start after editing openclaw.json
- A key the Gateway does not know stops it. Servers belong under mcp.servers in ~/.openclaw/openclaw.json, so move any block copied from another format, such as an mcpServers block, into that shape.
- The agent cannot see a file you can open in Drive
- Only picked files and files Ryze AI created are visible. Attach the file with Attach files > Upload from Drive in a Ryze AI chat.
- A file is attached by name only
- Files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides come back by name only. Images picked from Drive are not supported.
- A Doc lost its formatting
- writeDoc writes plain text, appended at the end or replacing the whole document, so headings, links and formatting are not kept.
- The agent says a subscription is required
- The tools need an active Ryze AI plan or free trial. Without one the connector can only list workspaces and connect platforms.
- You need a second Google account
- Drive connects one Google account per Ryze AI workspace. Disconnect Drive and connect it again with the other account.
Terms on this page
- Gateway
- OpenClaw's single process on your machine or server. It reads its server list from openclaw.json and keeps MCP sign-ins in its state directory.
- mcp.servers
- The section of ~/.openclaw/openclaw.json that lists the MCP servers OpenClaw connects to.
- Shared credentials
- OpenClaw's default for OAuth: one operator-managed sign-in per server that everyone talking to the agent uses.
- toolFilter
- A setting on a server entry that keeps (include) or hides (exclude) tools by exact name or * pattern.
- drive.file scope
- The Google permission that limits an app to files the user opens with it or shares with it through a picker, plus files the app creates.
- Google Picker
- Google's file-open dialog for Drive, which an app shows so the user can choose files.
- A1 notation
- The way to name Sheet cells: the tab name, then column letters and row numbers, as in Sheet1!A1:B2.
Sources: OpenClaw Gateway configuration, OpenClaw transports and OAuth, OpenClaw MCP config (checked November 15, 2026); Drive API scopes, Google Picker overview, Sheets concepts (checked November 14, 2026).
Frequently asked questions
How do I connect OpenClaw to Google Drive?
Connect Google Drive in a Ryze AI workspace and pick the files to share in a Ryze AI chat. Then stop the Gateway, run openclaw mcp set ryze with the URL https://connector.get-ryze.ai/mcp, transport streamable-http and auth oauth, and run openclaw mcp login ryze. Approve the sign-in, click Allow connection and start the Gateway again. An administrator can do the same from Settings > MCP in the Control UI without stopping the Gateway.
Is there a Google Drive MCP server for OpenClaw?
Yes, the Ryze AI connector at https://connector.get-ryze.ai/mcp, which OpenClaw saves as a remote server and which brings 7 Drive tools. Google also hosts a Drive MCP server in Developer Preview, but its setup page names Antigravity and Claude and not OpenClaw. Zapier and Composio list OpenClaw among their clients.
Is there a Google Drive connector for OpenClaw?
OpenClaw's MCP pages describe how to add servers and name no built-in Drive connector. ClawHub had no Ryze AI plugin on November 15, 2026, so the Ryze AI connector is added by its URL as a remote MCP server.
Can OpenClaw see all my Google Drive files?
No. The Google sign-in uses the drive.file scope, so OpenClaw reaches only files you pick in the Ryze AI chat and files Ryze AI created. It cannot search or browse the whole Drive, and files outside those two groups look like missing files.
Can OpenClaw edit Google Sheets and Docs?
Yes, within picked or Ryze AI created files. updateSheetValues overwrites cells, appendSheetValues adds rows, createFile makes new Sheets, Docs and text, CSV or JSON files, and writeDoc puts plain text into a Doc. Doc writes carry no headings, links or formatting.
Can OpenClaw delete files in Drive?
No. The Ryze AI connector has no delete tool, and its 4 write tools only overwrite, append or create. Zapier's Drive page lists a permanent delete action, if you need that elsewhere.
Does Google have its own Drive MCP server I can use with OpenClaw?
Google hosts one at https://drivemcp.googleapis.com/mcp/v1 with Streamable HTTP and OAuth 2.0, in Developer Preview since April 22, 2026. It needs a Google Cloud project and your own OAuth client, and it reads every file you can open. Google's setup page does not name OpenClaw, so which OpenClaw setting takes the client ID and secret was not confirmed.
Which Google Drive route should I pick for OpenClaw?
Pick the Ryze AI connector for one hosted URL and a narrow, picked-files scope. Pick Google's server to search every file you can open, or Zapier for move and delete actions. Each of the other routes asks for more setup than one remote entry and one sign-in.
Do I need a paid OpenClaw plan?
No. OpenClaw is open source (MIT license per its GitHub repository) and self-hosted, and its docs say it has no paid tier. The cost is the Ryze AI plan or trial that the Drive tools need.
Should I use OAuth or an API key?
OAuth through openclaw mcp login is the default path here. A Ryze AI API key sent as a bearer header suits setups where no browser sign-in is practical. OpenClaw ignores static Authorization headers while auth is set to oauth, so use one method per entry.
Why can OpenClaw not find a file I just uploaded to Drive?
A file you add in Drive itself is not visible until you pick it. Attach it with Attach files > Upload from Drive in a Ryze AI chat. Files Ryze AI created through createFile are reachable without that step.
Why does the server not appear in my OpenClaw agent?
Until shared credentials exist, OpenClaw leaves the server out of the agent runtime. Stop the Gateway, run openclaw mcp login ryze, start the Gateway again and check with openclaw mcp status.
What if OpenClaw runs on a server without a browser?
Open the sign-in link in a browser on another machine, approve it there and give the returned code to the --code option of openclaw mcp login. If the callback also carries an iss value, pass it with --issuer.
How much does it cost to connect OpenClaw to Google Drive?
Connecting costs nothing, but the 7 Drive tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, and SEO Starter is $129 per month with a 3-day free trial. Annual billing takes 30% off the first year.
How do I disconnect Google Drive from OpenClaw?
Stop the Gateway and run openclaw mcp logout ryze to drop the credentials, or openclaw mcp unset ryze to remove the entry. To end the Google access, disconnect Google Drive under Integrations in Ryze AI.