By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Hermes Agent to Google Drive is the Ryze AI connector. Connect Google Drive in a Ryze AI workspace and pick your files in the Ryze AI chat. Then add https://connector.get-ryze.ai/mcp under mcp_servers in ~/.hermes/config.yaml with auth: oauth, run hermes mcp login ryze, click Allow connection on the Ryze AI page and run /reload-mcp or start a new session. Hermes Agent then lists 7 Google Drive tools: 3 that read and 4 that write, with no delete tool. They reach only the files you picked and the files Ryze AI created.
- In Ryze AI open Integrations, find Google Drive under Files and click Connect
- In the Ryze AI chat pick your files with + > Attach files > Upload from Drive
- Add a ryze entry with the connector URL and auth: oauth under mcp_servers in ~/.hermes/config.yaml
- Run hermes mcp login ryze, click Allow connection on the Ryze AI page, then run /reload-mcp
Hermes Agent to Google Drive at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in Hermes Agent as a remote MCP server named ryze, with no Google Cloud project to set up |
| Server address | https://connector.get-ryze.ai/mcp, set as url: under mcp_servers in ~/.hermes/config.yaml |
| Sign-in | OAuth with auth: oauth, completed by hermes mcp login ryze. A Ryze AI API key in an Authorization header is the other route |
| Google Drive tools | 7 in all: 3 that read and 4 that write, with no delete tool |
| Which files it reaches | Files you pick in the Ryze AI chat and files Ryze AI created. The Google scope is drive.file, so there is no Drive-wide search or browsing |
| Can it change files | Yes. It can overwrite Sheet ranges, append rows, create files and write plain text into a Doc. tools.exclude on the ryze entry keeps chosen tools away from the agent |
| Other data in the same chat | Tools for the other platforms connected to your Ryze AI workspaces list under the same address. This guide covers Google Drive only |
| Hermes Agent plan | None to buy. Hermes Agent is open source and self-hosted, and its GitHub repository lists the MIT license |
| Ryze AI price | Connecting is free. The tools need an active plan or trial: Paid Ads is $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial, Agency $279 per month |
| Google's own option for Hermes Agent | Google hosts a Drive MCP server at https://drivemcp.googleapis.com/mcp/v1 in Developer Preview. Its setup page names Antigravity and Claude, not Hermes Agent, and it needs your own Google Cloud project and OAuth client |
| Last tested | 8 Google Drive calls went through the connector from Claude Code on November 14, 2026, none on a real file. Hermes Agent's docs were read on November 18, 2026. No step was run inside Hermes Agent |
Before you start
- Hermes Agent. It is open source and self-hosted by Nous Research, with no plan tier. You need a terminal on the machine that runs it and write access to ~/.hermes/config.yaml.
- A Google account that holds the files. Ryze AI signs in to one Google account per workspace for Drive. The sign-in asks for a single permission, drive.file, so you choose the files afterwards in a picker.
- 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. Connecting is free; the Google Drive tools need an active plan or trial. Annual billing takes 30% off the first year.
- A note on testing. Ryze AI has no help-center page for Hermes Agent and has not tested the connector there. The steps below follow Nous Research's MCP documentation for remote servers that use OAuth, as it read on November 18, 2026.
How to connect Hermes Agent to Google Drive
Two steps happen in Ryze AI and Google, the rest in Hermes Agent. 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.
Pick the files the agent may use
In the Ryze AI chat click + (Add to message), then Attach files, then Upload from Drive, and choose the Sheets, Docs or other files. Files outside the picker are invisible to the tools, apart from files Ryze AI created itself.
Add the connector to config.yaml
Open ~/.hermes/config.yaml and add a ryze entry under mcp_servers with url set to https://connector.get-ryze.ai/mcp and auth set to oauth, as in the block below. Do this before signing in. Hermes Agent's docs warn that editing config.yaml inside a running session reloads MCP connections with a 30 second timeout, which is too short for an interactive OAuth flow.
mcp_servers: ryze: url: "https://connector.get-ryze.ai/mcp" auth: oauthSign in with hermes mcp login
Run: hermes mcp login ryze. Hermes Agent prints an authorize URL and opens the browser when it can. Sign in on the Ryze AI page if asked, choose the workspace that holds your Google Drive connection and click Allow connection.
Finish the sign-in on a headless host if needed
On a server without a browser, open the printed authorize URL on another machine. Hermes Agent's docs say an interactive terminal also prints a line to paste the redirect URL, so copy the address the browser ends on and paste it at the prompt.
Reload and ask your first question
Start a new session or run /reload-mcp, which reloads the servers from config.yaml and refreshes the tool list. Then ask: Read the keyword list on the first tab of the Sheet I picked and group it by topic.
The Ryze AI help center article for Google Drive covers the Google side of the connection. The Hermes Agent side is covered by its MCP guide and GitHub repository.
Sources: Hermes Agent: MCP configuration, Hermes Agent on GitHub (checked November 18, 2026).
config.yaml, hermes mcp login and API key
config.yaml with OAuth
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauthThis is the flow in the steps above. The entry name ryze is yours to choose, and Hermes Agent prefixes the tools it finds with mcp_ and that name. hermes mcp login ryze runs the authorization and Hermes Agent caches the tokens at ~/.hermes/mcp-tokens/ryze.json, reusing them until a refresh fails. hermes mcp test ryze checks the connection, and hermes mcp configure ryze lets you pick which tools stay on.
A Ryze AI API key instead of OAuth
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
headers:
Authorization: "Bearer ${RYZE_API_KEY}"Leave out auth: oauth and send the key as a bearer header. Put RYZE_API_KEY, the rk_live_ key from Ryze AI, in ~/.hermes/.env instead of writing it into config.yaml; Hermes Agent resolves ${VAR} placeholders when it connects. Then run /reload-mcp. This route needs no browser, which suits a server you reach only over SSH.
Limit the tools with include and exclude
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
tools:
exclude: ["*updateSheetValues", "*appendSheetValues", "*createFile", "*writeDoc"]tools.include is a whitelist and tools.exclude a blacklist, and both accept glob patterns. The block above leaves the 3 read tools and drops the 4 write tools. After saving, run /reload-mcp and ask Hermes Agent to list its Ryze AI tools to confirm which ones remain. Whether the patterns match the bare tool name or the mcp_-prefixed name was not tested, so check the list.
Transport and timeouts
Hermes Agent's MCP page says each server entry accepts timeout for tool calls and connect_timeout for the first connection. Its example shows 30 and 60 seconds, and the page gives no default for either. A long Sheet read is the case to raise timeout for. Hermes Agent supports stdio servers and HTTP or SSE remote endpoints; the connector is a remote HTTP endpoint, so no local process is involved. HTTP servers honor HTTPS_PROXY, HTTP_PROXY and NO_PROXY.
Hermes Agent and MCP: the facts in one table
| Question | Answer from Hermes Agent's docs |
|---|---|
| Where a server is added | Under mcp_servers in ~/.hermes/config.yaml. hermes mcp opens an interactive picker and hermes mcp install <name> installs a catalog entry |
| Remote server format | url: for the address, then either headers: for a static token or auth: oauth for a browser sign-in |
| Transports | Stdio for local subprocesses, and HTTP or SSE for remote endpoints |
| Sign-in | hermes mcp login <server> authorizes OAuth 2.1 with PKCE and waits up to 5 minutes by default. Hermes Agent identifies itself with a Client ID Metadata Document where the server supports one and falls back to dynamic client registration, which is the route the Ryze AI connector uses |
| Saved credentials | Tokens are cached at ~/.hermes/mcp-tokens/<server>.json and reused until a refresh fails |
| Tool names | Prefixed as mcp_<server_name>_<tool_name>, so the connector's tools begin mcp_ryze_ |
| Tool selection | tools.include and tools.exclude with glob patterns, or hermes mcp configure <name> |
| Approval | The MCP page says Hermes Agent prompts for write operations by default unless trust is set to full. This was read, not tested with the connector |
| Plan | None. Open source and self-hosted |
| Reload and test | /reload-mcp reloads from config.yaml and refreshes the tool list. hermes mcp test <name> verifies a connection |
Sources: Hermes Agent: MCP configuration, Hermes Agent on GitHub (checked November 18, 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. Your picked files stay the same in every client.
Claude Code
Claude Code registers the same URL with one claude mcp add command. See the Claude Code guide for Google Drive.
OpenClaw
OpenClaw, another self-hosted agent, saves the connector with its own commands.
ChatGPT and Claude
Both take the URL as a custom connector in their settings, with plan limits that Hermes Agent does not have.
Permissions and access
Four things decide what Hermes Agent can see and change in Drive.
- Single Drive scope
- Ryze AI asks Google for drive.file and nothing broader, and it keeps no API key or service account for Drive.
- File reach
- Files chosen in the Google picker inside the Ryze AI chat composer, plus files Ryze AI made itself. A chosen Sheet opens as a whole, with every tab.
- Shared sign-in
- The Hermes Agent tokens sit in ~/.hermes/mcp-tokens/ on the host. Anyone who can talk to that agent works through the same Ryze AI sign-in and the same chosen files.
- Google account
- Drive links one Google account to each workspace. A different account means disconnecting Drive in Ryze AI and connecting again.
What the connection is allowed to do
Two sign-ins stand between Hermes Agent and your files. Hermes Agent signs in to the Ryze AI connector, and Ryze AI holds a Google sign-in for Drive. The Google side carries one scope, shown first below in Google's own words, followed by wider scopes that are not part of the connection.
| Google scope | How Google describes it | In the connection |
|---|---|---|
| https://www.googleapis.com/auth/drive.file | Drive API page: "Create new Drive files, or modify existing files, that you open with an app or that the user shares with an app while using the Google Picker API or the app's file picker." | Yes. Google lists it as a non-sensitive scope |
| https://www.googleapis.com/auth/drive | "View and manage all your Drive files." Restricted scope | No |
| https://www.googleapis.com/auth/drive.readonly | "View and download all your Drive files." Restricted scope | No |
| https://www.googleapis.com/auth/spreadsheets | "See, edit, create, and delete all your Google Sheets spreadsheets." Sensitive scope | No |
| https://www.googleapis.com/auth/documents | "See, edit, create, and delete all your Google Docs documents." Sensitive scope | No |
What the default connection does not include: files you did not pick, Drive-wide search or browsing, a delete or trash tool, images picked from Drive, files over 10 MB, binary files and Google formats other than Sheets, Docs and Slides (these come back by name only), formatted Doc writes, a section-level Doc edit, and a second Google account in the same workspace. Between Hermes Agent and the connector, the connector's sign-in data lists the scopes mcp:read and mcp:write.
Sources: Google Drive API scopes, Google Drive Picker overview, Google Sheets API scopes (checked November 14, 2026).
Removing access
To cut Hermes Agent off, delete the ryze entry from mcp_servers in ~/.hermes/config.yaml, run /reload-mcp and delete ~/.hermes/mcp-tokens/ryze.json. The Hermes Agent docs describe no logout command, so removing the entry and the token file is the manual route. To disconnect Drive itself, disconnect Google Drive on its card in Ryze AI, or withdraw the access on your Google Account permissions page (myaccount.google.com/permissions).
What Hermes Agent can do in Google Drive
The Ryze AI connector exposes 7 Google Drive tools: 3 that read and 4 that write, and none that delete. The tool definitions seen on November 14, 2026 show that on a connector sign-in covering several Ryze AI workspaces, each tool also takes a required workspace argument.
| Tool | Type | What it does |
|---|---|---|
| listFiles | Read | Returns the files in Drive that the connection can open, most recent first. An optional Drive search term narrows the list. |
| readFile | Read | Opens one file by its ID. A Sheet comes back as cell values, a Doc or a Slides deck as plain text, and a text, CSV or JSON file as its content. |
| getSheetValues | Read | Returns the cell values of one tab or one A1 range of a Sheet. |
| updateSheetValues | Write | Replaces the cells in a given range of a Sheet with new values. Formulas are accepted. |
| appendSheetValues | Write | Adds new rows under the last row of a table in a Sheet. |
| createFile | Write | Makes a new Sheet, Doc, text, CSV or JSON file in your Drive and hands back its link. |
| writeDoc | Write | Puts plain text into a Doc, either after the existing text or in place of all of it. |
Keeping the write tools out of reach
Hermes Agent's MCP page says it prompts for write operations by default unless trust is set to full, but that was not tested with this connector, so the control to rely on is which tools the agent sees. updateSheetValues and writeDoc can replace existing content, so the standing way to keep the four write tools out of reach is tools.exclude on the ryze entry, as in the third block above, or tools.include with only the read tool names, as below. hermes mcp configure ryze does the same interactively. In the Ryze AI chat itself, changes follow its Tool approvals setting, which starts on Skip all approvals.
mcp_servers:
ryze:
url: "https://connector.get-ryze.ai/mcp"
auth: oauth
tools:
include: ["*listFiles", "*readFile", "*getSheetValues"]Limits in numbers
| Limit | Figure or rule | Set by |
|---|---|---|
| Drive API quota | 1,000,000 quota units a minute for the project and 325,000 a minute for each user. Cloud projects created from May 1, 2026 get these quotas, and older projects keep theirs | |
| Price of a Drive call | Reads cost 5 quota units, lists 100, edits 50, downloads and exports 200 | |
| Past the Drive quota | 403: User rate limit exceeded, or sometimes 429: Rate limit exceeded. Google advises truncated exponential backoff | |
| Sheets API | 300 reads and 300 writes a minute per project, and 60 of each per user. Past that, 429: Too many requests | |
| Docs API | Reads 3,000 a minute per project and 300 per user. Writes 600 a minute per project and 60 per user | |
| Drive file ceilings | Docs hold 1.02 million characters, Sheets 20 million cells or 100 MB, any other file 5 TB | |
| Sheet rows per read | getSheetValues stops at 10,000 rows. Ask for the next block with an explicit range such as 'Sheet1'!A10001:D20000 | Ryze AI |
| Readable file size | readFile gives content: null for binary files, other Google formats and anything over 10 MB | Ryze AI |
| Argument lengths | IDs run 1 to 200 characters, range 1 to 300, the listFiles query 1 to 500 | Ryze AI |
| Write sizes | createFile takes a name up to 300 characters and content up to 200,000. writeDoc takes 1 to 200,000 characters | Ryze AI |
| Reload after an edit in a session | A 30 second timeout, too short for an interactive OAuth sign-in | Hermes Agent |
| Sign-in wait | hermes mcp login waits up to 5 minutes by default | Hermes Agent |
The Google rows bind any app that calls the Drive, Sheets and Docs APIs. Ryze AI's facts do not say which Google quota set applies to the project behind the connector, and none of the test answers carried a quota or rate figure, so this guide does not claim one applies to the connector. They apply directly if you run Google's own server with your own project.
Sources: Drive API limits, Sheets API limits, Docs API limits, Drive file sizes (checked November 14, 2026); Hermes Agent: MCP configuration (checked November 18, 2026).
Google Drive calls through the connector, tested
On November 14, 2026 the Ryze AI connector took 8 Google Drive calls from Claude Code, on a real workspace's Drive connection. Hermes Agent was not the client, but it reaches the same server and the same tools. Every call was built so that it could not return a real file: a filter that matches nothing, IDs that do not exist, a field that does not exist, a page token that does not exist, and values over the allowed length. No file was listed or read.
| Call | Tool | Outcome |
|---|---|---|
| Name filter that matches no file | listFiles | Succeeded with an empty result, {"files":[]}, and no paging token |
| File ID that is not in Drive | readFile | Came back as not_found with a File not found message |
| Spreadsheet ID that is not in Drive, range Sheet1!A1:B2 | getSheetValues | Came back as not_found |
| No-match filter combined with an unknown field name | listFiles | Google answered Error 400, Invalid Value, location q |
| No-match filter combined with an invented page token | listFiles | Google answered Error 400, Invalid Value, location pageToken |
| File ID padded to 201 characters | readFile | The connector stopped it before Google: invalid_arguments, maximum 200 |
| Filter padded to 501 characters | listFiles | The connector stopped it before Google: invalid_arguments, maximum 500 |
| Unknown spreadsheet ID with a blank range | getSheetValues | The connector stopped it before Google: invalid_arguments, minimum 1 |
No answer carried a quota counter or a rate-limit header, and no limit was reached. The only figures that came back were the 200, 500 and 1 in the refusals above.
First 3 prompts to run
Each answer comes from your own files, so this page describes what comes back instead of showing sample data.
1. Turn a keyword Sheet into topic groups
Open the first tab of the Sheet I picked, read the keywords in column A and sort them into topic groups.
Tools used: getSheetValues
What comes back: The values of that tab as stored in your own Sheet, up to 10,000 rows per call, ready for Hermes Agent to group. The Sheet must be one you picked or one Ryze AI created.
2. Save a summary as a new Doc
Make a new Google Doc named Weekly report and put this summary into it as plain text.
Tools used: createFile, writeDoc
What comes back: A fresh Doc in your Drive and its link. The text lands without headings, links or formatting.
3. Extend a log Sheet
Add these three rows under the last row of the table in my log Sheet.
Tools used: appendSheetValues
What comes back: Three new rows below the table in the Sheet you picked. The rows already there stay untouched.
Write calls change real files, and updateSheetValues replaces the cells in the range it is given. Say the range and the values in plain words, and check the tool list in Hermes Agent first if you excluded the write tools.
10 jobs to hand to Hermes Agent
Ten jobs to give a Hermes Agent session, each matched to the tool behind it. In the November 14 test only the empty list came back as a result, so every row follows Ryze AI's tool list, not a run on a real file. Every job needs an active Ryze AI plan or trial, and the write jobs need the write tools to stay in the agent's tool list.
| Job | What to ask Hermes Agent | Tool | Default connection |
|---|---|---|---|
| Pull a keyword list | Read the keyword tab of my picked Sheet and list what is in it. | getSheetValues | Yes for a picked or Ryze AI created Sheet, 10,000 rows per call |
| See what is reachable | Show me the Drive files you can open, latest first. | listFiles | Yes, but the list holds picked and Ryze AI created files, never the whole Drive |
| Summarize a brief | Open the picked Doc and give me a short summary. | readFile | Yes, as text |
| Summarize a deck | Read the text of the picked deck and summarize slide by slide. | readFile | Yes, as plain text |
| Describe a CSV | Open the picked CSV and tell me what each column holds. | readFile | Yes for a picked file up to 10 MB; bigger and binary files return a name only |
| File a report as a Doc | Create a Doc and put this report inside. | createFile, then writeDoc | Yes, in plain text without headings, links or formatting |
| Log the week | Add this week's rows to the log Sheet. | appendSheetValues | Yes for a picked or created Sheet; rows go under the last table row |
| Rewrite a range | Replace A1:C10 with these values and these formulas. | updateSheetValues | Yes; whatever sat in the range is replaced |
| Build a table Sheet | Create a new Sheet and fill it with this table. | createFile, then updateSheetValues | Yes, in two calls: an empty Sheet first, then the values, and the link returns |
| Store output as CSV | Save this output as a CSV file in my Drive. | createFile | Yes, with the content inline up to 200,000 characters |
Jobs the connection cannot do: delete or trash a file (no delete tool), search or browse the whole Drive (drive.file scope), read an image or a PDF from Drive, write a formatted Doc or edit one section in place, and use two Google accounts in one workspace.
3 ways to connect Hermes Agent to Google Drive
Several ways can give Hermes Agent your Drive files. This guide treats the first, the Ryze AI connector, as the main way: the Google sign-in happens once inside Ryze AI, with no Google Cloud project or OAuth client of your own, and the Hermes Agent side is one remote entry in config.yaml. The others were read on their own pages on November 14, 2026, and none was installed in Hermes Agent.
| Way | Runs where | Setup in Hermes Agent | What it reaches in Drive | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI, one address for every user | A ryze entry under mcp_servers with url and auth: oauth, then hermes mcp login ryze. A Ryze AI API key in an Authorization header can stand in for the sign-in. Files are picked in the Ryze AI chat | 7 tools: list, read Sheets, Docs, Slides and text files, read Sheet ranges, overwrite or append Sheet values, create files and write plain text into Docs. Only picked files and files Ryze AI created. No delete tool | Free to add. The tools need an active plan or trial: Paid Ads $89 per month with a 7-day free trial, SEO Starter $129 per month with a 3-day free trial, Agency $279 per month |
| Google Drive MCP server, hosted by Google | Google hosts it at https://drivemcp.googleapis.com/mcp/v1 over Streamable HTTP with OAuth 2.0. It is in Developer Preview | Google's setup page documents Antigravity and Claude and gives a generic section for other clients. For Hermes Agent this would be a url entry with auth: oauth and your own OAuth client, which was not tried. Setup needs the Developer Preview Program, a Google Cloud project, two enabled APIs, drive.readonly and drive.file on the consent screen, and an OAuth client marked Use this client for an AI-powered agent | 8 tools. Six read: search_files, read_file_content, list_recent_files, download_file_content, get_file_metadata and get_file_permissions. Two write: create_file and copy_file. It sees every file you can open, minus files that fail Google's eligibility checks. No delete, move, rename or share tool, and no tool that edits an existing file | No separate price on Google's pages. A Google Cloud project and Developer Preview membership are required |
| Google Sheets, Docs and Slides MCP servers, hosted by Google | Google hosts each at its own address, for example sheetsmcp.googleapis.com/mcp/v1 and docsmcp.googleapis.com/mcp/v1. Developer Preview | The same steps as the Drive server, repeated per product with that product's scopes and an agent-marked OAuth client. Each server is its own entry. Not tried with Hermes Agent | Sheets, 6 tools including update_values and update_formulas. Docs, 2 tools: read_doc and update_doc. Slides, 4 tools on the reference page. These edit formatting and structure, which the Ryze AI Drive tools do not | No separate price on Google's pages |
| Composio | Hosted by Composio | Composio lists Hermes among the agents on its Google Drive page. Whether its steps cover Hermes Agent's config.yaml was not checked. A Composio sign-in and a Google Drive connection happen on first use through its managed OAuth app | The page lists 92 tools and 7 triggers for Google Drive, read and write, including file and folder tools and spreadsheet value tools | Composio's pricing page lists a free plan with 10,000 tool calls per month and Standard at $18 per seat per month. Its Drive page gives a different free allowance, so check both |
| Zapier MCP | Hosted by Zapier | Zapier's Drive page and quickstart name clients such as Claude, ChatGPT, Cursor and Codex, and Hermes Agent is not among them. Its server is a URL, so a remote entry is plausible, but that was not tried | The Google Drive actions enabled in your Zapier account. The page shows Copy File, Delete File (Permanent), Export File, Upload File, Create Folder, Move File, Create File From Text and Remove File Permission before a Load More button, and states no total | Each successful tool call uses 2 tasks from your Zapier plan; failed calls do not count |
Options that do not fit Hermes Agent
- Claude's Google Drive connector and ChatGPT's Google Drive app. Anthropic and OpenAI each document theirs for their own assistant, so neither can be added to Hermes Agent.
- The Google Workspace app inside Gemini. It serves the Gemini apps and does not run in Hermes Agent.
- Gemini CLI's Workspace extension and the gws command-line tool. Their pages name Gemini CLI and OpenClaw, not Hermes Agent. The gws README calls itself an unofficial Google project.
- workspace-mcp by taylorwilsdon. A Python server you host with your own Google Cloud OAuth client and a read-only mode. Its README lists Claude Desktop, Claude Code, ChatGPT, Codex, VS Code, LM Studio and Open WebUI, and Hermes Agent is absent.
- @modelcontextprotocol/server-gdrive. The old reference server, marked unsupported on npm and archived on GitHub in May 2025. Google does not publish it.
Which one to pick
Ryze AI is the best way to connect Hermes Agent to Google Drive when you want an agent to read picked Sheets and Docs and write results back through one hosted address, with four caveats: the tools reach only files you picked or that Ryze AI created, Doc writes are plain text, the tools need a Ryze AI plan once the trial ends, and files are picked in the Ryze AI chat, not in Hermes Agent. Pick Google's own Drive server when the agent must search and read your whole Drive and you can run a Google Cloud project and an agent-marked OAuth client, accepting that it is a Developer Preview that cannot edit existing files. Pick Google's Sheets, Docs and Slides servers for formatting and structure edits. Composio fits a team that wants a large Drive tool list, and Zapier fits a team whose Drive tasks already run through Zapier. The connector and Google's servers can sit in one config.yaml under different names. Try any of them on a test folder before it touches real files.
Sources: Google Drive MCP server setup, Google Drive MCP reference, Google Drive MCP file eligibility, Google Workspace MCP servers, Composio Google Drive, Composio pricing, Zapier Google Drive MCP, Zapier MCP quickstart, google_workspace_mcp, Google Workspace CLI (checked November 14, 2026); Hermes Agent: MCP configuration, Hermes Agent on GitHub (checked November 18, 2026).
Google Drive and Hermes Agent: dates that matter
| Date | What happened |
|---|---|
| April 22, 2026 | Google's release notes introduced its Google Drive MCP server as a Developer Preview. |
| May 21, 2026 | Google added a copy_file tool to that Drive server. |
| July 13, 2026 | Google opened Docs, Sheets and Slides MCP servers in Developer Preview. |
| October 1, 2026 | Comment reading and management reached the Docs, Sheets and Slides servers, and the Slides server picked up two page-level read tools. |
| October 12, 2026 | Google told developers that OAuth clients calling the Drive MCP server must tick Use this client for an AI-powered agent. |
| November 5, 2026 | Hermes Agent v0.23.0 shipped pluggable delegation and plugin self-updates. |
| November 10, 2026 | Hermes Agent v0.23.1 raised the plugin catalog size cap from 2 MiB to 16 MiB. |
| November 11, 2026 | That agent-client rule took effect for Google's Workspace MCP servers. |
| November 13, 2026 | Google refreshed the page that lists which Drive files an AI agent may use. |
| November 16, 2026 | Hermes Agent v0.23.2 shipped as the stable release. Its GitHub releases page listed canary builds through November 18, 2026, and the notes read named no change to how remote MCP servers connect. |
Sources: Google Workspace release notes, Drive MCP file eligibility, Drive API limits, Reference server on npm, Archived reference servers (checked November 14, 2026); Hermes Agent releases (checked November 18, 2026).
How this guide was tested
Two dates stand behind this guide. On November 14, 2026 the 7 Google Drive tool definitions were loaded and 8 Google Drive calls went through the connector from Claude Code. On November 18 Hermes Agent's MCP documentation and releases page were read and compared with the setup steps. Nothing was run inside Hermes Agent.
| What was run | What came back |
|---|---|
| Tool definitions, November 14 | 7 Google Drive tools under the names in the tools table: 3 read, 4 write, no delete tool. No other google_drive tool was listed. |
| Empty list, November 14 | listFiles with a name filter that matches nothing worked and returned {"files":[]}. |
| Calls built to be refused, November 14 | Seven, each answered with a message listed in the errors table below. |
| Quota and rate limits, November 14 | No answer carried a quota counter or a rate-limit header, and no limit was reached. |
| Hermes Agent MCP documentation, November 18 | The page shows url with headers or auth: oauth, hermes mcp login, test and configure, tools.include and tools.exclude with globs, timeout and connect_timeout, /reload-mcp and the mcp_<server>_<tool> prefix. |
Not run for this page: every step inside Hermes Agent. It was not installed, no config.yaml entry was saved, hermes mcp login and /reload-mcp were not tried, and the tools.include and tools.exclude patterns were not matched against real tool names. Those steps follow Hermes Agent's documentation as it read on November 18, 2026. The tool calls came from Claude Code, which reaches the same connector and the same 7 tools. No real file was listed or read, none of the 4 write tools was called because they change files, and the Ryze AI Drive picker was not used. Composio and Zapier were read on their own pages and not installed.
Errors and fixes
Exact messages from the connector test
These messages came back word for word in the test on November 14, 2026. 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 a Hermes Agent session, this is what it means.
| Message | Meaning | What to do in Hermes Agent |
|---|---|---|
| File not found: <redacted>. | readFile returned not_found. Either no such file ID exists, or the file was neither picked in Ryze AI nor created by it. Under drive.file those two cases look identical. | Pick the file in the Ryze AI chat through Attach files, then Upload from Drive, and ask again. |
| Requested entity was not found. | getSheetValues returned not_found: the spreadsheet ID does not exist, or the connection cannot reach that Sheet. | Pick the Sheet in the Ryze AI picker, or have Hermes Agent run listFiles to find the ID of a reachable Sheet. |
| Invalid Value (Error 400, location: q) | Google rejected the listFiles search term as invalid query syntax, here because of a field name that does not exist. | Use a plain term such as name contains 'KPI', or send no filter. |
| Invalid Value (Error 400, location: pageToken) | Google rejected a page token that no earlier list call produced. The message matches the bad filter, and only the location differs. | Run the list again without a page token. |
| Too big: expected string to have <=200 characters | An ID over 200 characters was refused before reaching Google (path: fileId), which usually means a whole link was pasted as the ID. | Send only the ID portion of the link. |
| Too big: expected string to have <=500 characters | A search term over 500 characters was refused before reaching Google (path: query). | Cut it down to a single name contains term. |
| Too small: expected string to have >=1 characters | A blank range was refused (path: range). getSheetValues wants a tab title or an A1 range and does not accept named ranges. | Give a tab name such as Sheet1 or a range such as Sheet1!A1:D50. |
Other problems
- No Google Drive tools show up
- Run hermes mcp test ryze, then /reload-mcp or open a new session. If the entry uses auth: oauth and you never signed in, run hermes mcp login ryze first. A cached tool list can predate the Drive connection, so confirm the Google Drive card in Ryze AI reads Connected.
- The sign-in breaks after a config.yaml edit mid-session
- Hermes Agent reloads MCP 30 seconds after an in-session edit, too little time for an interactive OAuth flow. Save the entry and run hermes mcp login ryze from a terminal.
- The authorize page opens on another machine, or never opens
- Paste the printed authorize URL into a browser elsewhere, approve it, then paste the redirect URL at the prompt an interactive terminal shows.
- Tool names look long
- Hermes Agent names each tool mcp_<server>_<tool>, so connector tools start with mcp_ryze_. Begin include and exclude patterns with * to match either form.
- The API key is ignored
- Confirm RYZE_API_KEY sits in ~/.hermes/.env and the header reads Bearer plus the placeholder. Run /reload-mcp after each change and remove auth: oauth if you use the key.
- A sign-in that worked now fails
- Hermes Agent keeps using a cached token until a refresh fails. Delete ~/.hermes/mcp-tokens/ryze.json and run hermes mcp login ryze again.
- A file is invisible to the agent
- Only picked files and files Ryze AI created can be seen. Pick the file in the Ryze AI chat. Images, files over 10 MB and binary files return a name alone.
- A Doc lost its headings
- writeDoc inserts plain text. Headings, links and formatting are not supported, and replace mode overwrites the whole document.
- A second Google account is needed
- Disconnect Drive in Ryze AI and connect the other account, since a workspace holds one.
- Tools ask for a subscription
- The Drive tools need an active Ryze AI plan or free trial. Start the trial and retry.
- A proxy blocks the connection
- HTTP servers honor HTTPS_PROXY, HTTP_PROXY and NO_PROXY, so set them where Hermes Agent runs.
Terms on this page
- MCP
- Model Context Protocol, the open standard that lets an assistant such as Hermes Agent call tools hosted elsewhere.
- mcp_servers
- The section of ~/.hermes/config.yaml listing the MCP servers Hermes Agent connects to, one named entry each.
- auth: oauth
- A Hermes Agent setting marking an HTTP server as browser sign-in, finished with hermes mcp login.
- /reload-mcp
- A Hermes Agent command that rereads config.yaml and refreshes the tool list inside the running session.
- drive.file
- A Google permission limiting an app to files a user opens with it through a picker, plus files it creates.
- Google Picker
- Google's file-open dialog. In Ryze AI it sits in the chat composer under + > Attach files > Upload from Drive.
- A1 notation
- Cell naming for Sheets: tab name, column letters, row numbers, as in Sheet1!A1:B2.
Sources: Hermes Agent: MCP configuration (checked November 18, 2026); Google Drive Picker overview, Google Sheets concepts (checked November 14, 2026).
Frequently asked questions
How do I connect Hermes Agent to Google Drive?
Connect Google Drive in a Ryze AI workspace, pick your files in the Ryze AI chat, then add a ryze entry with url https://connector.get-ryze.ai/mcp and auth: oauth under mcp_servers in ~/.hermes/config.yaml. Run hermes mcp login ryze, click Allow connection and run /reload-mcp.
Is there a Google Drive connector for Hermes Agent?
Yes, several. The Ryze AI connector at https://connector.get-ryze.ai/mcp goes into config.yaml as one remote entry. Google's own Drive MCP server is a Developer Preview that needs your own Google Cloud project, and Composio lists Hermes among the agents on its Drive page.
Is there a Google Drive MCP server for Hermes Agent?
Yes. Google hosts a Drive MCP server at https://drivemcp.googleapis.com/mcp/v1, but its setup page names Antigravity and Claude, not Hermes Agent, and it needs a Google Cloud project and your own OAuth client. The Ryze AI connector needs no project. Neither was run inside Hermes Agent for this guide.
What is a Google Drive MCP server?
A server that lets an AI client such as Hermes Agent call Google Drive tools over the Model Context Protocol. The Ryze AI one has 7 tools that list and read files, read and write Sheet values, create files and write plain text into Docs.
Which Google Drive MCP is best for Hermes Agent?
It depends on the file reach you need. The comparison on this page puts the Ryze AI connector first for picked-file reads and writes through one hosted address, Google's own Drive server first for reading a whole Drive, and Google's Sheets, Docs and Slides servers first for formatting edits.
Where does the Hermes Agent MCP config go?
Under mcp_servers in ~/.hermes/config.yaml. A remote server takes a url plus either headers or auth: oauth. hermes mcp opens an interactive picker if you prefer not to edit the file.
Which Hermes Agent plan do I need for MCP?
None. Hermes Agent is open source and self-hosted, and its GitHub repository lists the MIT license. The costs are the machine you run it on and the Ryze AI plan for the Drive tools.
Can I use an API key instead of the browser sign-in?
Yes. Leave out auth: oauth, add headers with Authorization set to Bearer ${RYZE_API_KEY}, and put the rk_live_ key in ~/.hermes/.env. This suits a server you reach only over SSH.
Can Hermes Agent see all my Drive files?
No. Through the Ryze AI connector it sees only the files you pick in the Ryze AI chat and the files Ryze AI created, because the Google scope is drive.file. There is no Drive-wide search or browsing.
Can Hermes Agent edit my Sheets and Docs?
Yes, within the picked files. It can overwrite a Sheet range, append rows, create files and write plain text into a Doc, appended or replacing the whole document. Doc writes carry no headings, links or formatting.
Can Hermes Agent delete Drive files?
No. The connector has no delete tool, so a Hermes Agent session cannot trash a file through it.
How do I stop Hermes Agent from changing files?
Add tools.exclude on the ryze entry with the four write tool names, or tools.include with only listFiles, readFile and getSheetValues, then run /reload-mcp. hermes mcp configure ryze does the same interactively.
Was this tested in Hermes Agent?
No. Eight Drive calls went through the connector from Claude Code on November 14, 2026, none on a real file, and Hermes Agent's documentation was read on November 18, 2026. Ryze AI has no help-center page for Hermes Agent.
How much does it cost?
Adding the connector costs nothing, but the 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?
Delete the ryze entry from mcp_servers, run /reload-mcp and delete ~/.hermes/mcp-tokens/ryze.json. Then disconnect Google Drive on its card in Ryze AI, or remove the access on your Google Account permissions page.