By Ira Bodnar, Ryze AI · Updated · Connector tested November 14, 2026
Quick answer
The main way to connect Muse to Google Drive is the Ryze AI connector. Connect Google Drive in a Ryze AI workspace, pick the files you want in the Ryze AI chat, then ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, follow its guided setup and sign in to Ryze AI when the link arrives. Muse then has 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
- In a Muse chat, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp
- Open the sign-in link Muse sends, choose the workspace and click Allow connection
Muse to Google Drive at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, created by asking Muse in a chat. No Google Cloud project and nothing to host |
| Server address | https://connector.get-ryze.ai/mcp |
| Where Muse is available | The US and Canada, per Meta |
| How the connector is added | Muse creates it from a chat request and runs a guided setup. Meta's pages describe no settings field for a server URL |
| Sign-in | A link Muse sends back opens the Ryze AI sign-in, where you pick workspaces and click Allow connection |
| Google Drive tools | 7 in all: 3 read and 4 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 Muse change files | Yes: it can overwrite Sheet ranges, append rows, create files and write plain text into a Doc. Meta says Muse does not take many important actions without approval by default |
| Other tools on the same URL | Tools for the other platforms connected to your Ryze AI workspaces list under the same address. This guide covers Google Drive only |
| Muse plan needed | Meta's help and newsroom pages reviewed name no plan for custom connectors |
| Ryze AI price | Adding the connector costs nothing. 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 Muse | The Google Drive MCP server at https://drivemcp.googleapis.com/mcp/v1, in Developer Preview. Google's setup pages name Antigravity and Claude, not Muse |
| Last tested | 8 Google Drive calls went through the connector from Claude Code on November 14, 2026, none on a real file. Nothing was run inside Muse |
Before you start
- A Muse account in the US or Canada. Meta says Muse is offered in those two countries only. The help and newsroom pages reviewed name no plan for custom connectors, so none is claimed here.
- 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.
How to connect Muse to Google Drive
Ryze AI takes the first two steps, and Muse the other four. Everyone uses the same connector URL.
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 Muse 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.
Ask Muse to create the custom connector
In a Muse chat on the web or in the app, ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp. The Ryze AI page at ryze.ai/muse has a ready-made message you can paste. Meta describes no settings field for a server URL, so the chat request is the route.
Follow Muse's guided setup
Muse walks you through setting up the connector and sends back a sign-in link. Meta says setup can involve retrieving API information from the service, and Muse keeps the credentials in its Secure Credentials Store.
Sign in to Ryze AI and allow the connection
Open the link, sign in on the Ryze AI page, choose the workspace that holds your Google Drive connection and click Allow connection.
Check approvals and ask your first question
Muse settings control how much it does without asking. Then ask: Read the keyword list on the first tab of the Sheet I picked and group it by topic. To change or remove the connector later, open Settings, then Connectors in Muse.
The Ryze AI help article for Google Drive covers the Google side of the connection and the file picker, and Meta describes custom connectors in its Muse help article.
Sources: Meta help: Muse connectors, Ryze AI Muse page. Checked November 8, 2026. Ryze AI Google Drive guide. Checked November 14, 2026.
Where Muse is available
Meta introduced Muse for small businesses in a newsroom post dated September 29, 2026, and says Muse is available in the US and Canada. The post lists connectors to services such as Shopify, Slack and Stripe and says custom connectors cover services Meta does not support yet. Google Drive was not among the services named in that post.
Muse is a chat assistant with no code editor or command line side in the pages reviewed, so there is one place to connect: the chat on the web or in the app. If you work in a code editor, see the Claude Code and Codex guides linked in Related guides below.
Muse and connectors: the facts in one table
| Topic | What Meta and Ryze AI say |
|---|---|
| How a connector is created | By asking Muse in a chat to create a custom connector, then following the guided setup it starts |
| Server URL field | None described. Meta's pages never mention MCP or a field for a server address |
| Where Ryze AI's connector details come from | The Ryze AI page at ryze.ai/muse, updated September 24, 2026: MCP over HTTP with an OAuth sign-in. Meta's pages do not confirm this, and it was not verified independently |
| Credentials | Muse stores them in its Secure Credentials Store, per Meta |
| Approval | By default Muse does not take many important actions without approval. Meta says the approval behavior is changed in Settings |
| Meta's newsroom on actions | Nothing publishes, sends or spends without your approval |
| Reviewing connectors | Meta does not review custom connectors or how they use data |
| Where connectors are managed | Muse Settings, then Connectors |
| Availability | The US and Canada |
| Plan | Meta's pages reviewed name none for custom connectors |
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
Claude and ChatGPT
Other MCP clients accept the same URL, and the Google connection made in Ryze AI stays as it is.
Claude
Add the same URL under Customize, Connectors, Add custom connector, then pick the workspace and start a new chat. Claude caches the tool list when you add the connector, so if you connected Google Drive in Ryze AI afterwards, remove the connector, add it again and open a new chat. In Claude, write tools can be set to Needs approval under Customize > Connectors > Ryze AI > Tool permissions.
ChatGPT
OpenAI lists full custom MCP support for Business and Enterprise/Edu workspaces on ChatGPT web, with Pro limited to read and fetch permissions. The steps are in the ChatGPT guide linked below.
Google Drive permissions
The Google side of the connection is one Google sign-in inside Ryze AI. Muse adds a second sign-in for the Ryze AI connector itself and its own approval setting, and Meta says it does not review custom connectors. Four things decide what Muse can see and change.
- Scope requested
- Google is asked for drive.file during the Ryze AI sign-in, and for nothing broader. Drive has no API key or service account on the Ryze AI side.
- Reach inside Drive
- The files chosen in the picker inside the Ryze AI chat composer, plus anything Ryze AI itself made. Picking a Sheet exposes the whole spreadsheet with every tab, because Google attaches Sheets scopes to the file.
- Read versus write
- One scope covers all 7 tools. The facts name no read-only mode for the connection, so Muse's own approval setting is the lever for slowing down the 4 write tools.
- Google account
- A workspace holds one Google account for Drive. Switching means disconnecting Drive in Ryze AI and signing in with the other account.
The access layers between Muse and a file
Several sign-ins sit between a Muse chat and a file in Drive. Read the table from Muse down to Google.
| Layer | What it allows | Where it is set |
|---|---|---|
| Muse to the Ryze AI connector | A sign-in on the Ryze AI page that Muse's link opens. The connector offers two scopes, mcp:read and mcp:write | The sign-in link from Muse |
| Ryze AI workspace | The workspace you allow there | The Allow connection screen |
| Ryze AI to Google | A Google sign-in with one scope, drive.file. Google lists it as a non-sensitive scope and describes it as access to the specific files you use with the app | Integrations, Google Drive, Connect |
| Which files | Files picked in the Google Drive picker in the Ryze AI chat and files Ryze AI created | + > Attach files > Upload from Drive in the Ryze AI chat |
| Muse approvals | By default Muse does not take many important actions without approval | Muse Settings |
Google's Drive scopes page says the drive.file scope "lets users choose which files they want to share with your app" and works with all Drive API resources. Google describes drive.file as covering deletion of the app's own files, yet the Ryze AI connector exposes no delete tool, so Muse cannot trash a file through it.
What the connection does not include
- Unpicked files. The drive.file scope rules out searching or browsing the rest of Drive. Google's own server adds drive.readonly and sees whatever you can open.
- Deleting. No tool trashes or removes a file.
- Pictures and heavy files. Images from Drive are unsupported. Anything over 10 MB, any binary file and any Google format besides Sheets, Docs and Slides shows up by name alone.
- Styled Docs. writeDoc takes plain text and either appends it or replaces the document. Headings, links and one-section edits are not possible.
- Two Google accounts at once. One account per workspace.
Sources: Google Drive scopes, Google Sheets scopes, Google Picker overview, Ryze AI Google Drive guide. Checked November 14, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026.
Removing access
To remove access, disconnect Google Drive on its card in Ryze AI Integrations, or withdraw the access on your Google Account permissions page (myaccount.google.com/permissions). In Muse, manage or disconnect the connector under Settings, then Connectors.
What Muse can do in Google Drive
Muse gets 7 Google Drive tools from the Ryze AI connector: 3 that read and 4 that write, and none that delete. Each full name starts with google_drive__. 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 the app can reach, newest first. A Drive search filter is optional. |
| readFile | Read | Opens one file by its ID: cell values for a Sheet, plain text for a Doc or Slides deck, raw content for text, CSV or JSON. |
| getSheetValues | Read | Pulls cell values from a range or a whole tab of a Sheet. |
| updateSheetValues | Write | Replaces the cells in a range with new values. Formulas are accepted. |
| appendSheetValues | Write | Adds rows beneath the last row of a table in a Sheet. |
| createFile | Write | Makes a new Sheet, Doc, or 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. |
Meta says Muse does not take many important actions without approval by default, and that you change the approval behavior in Settings. Its newsroom adds that nothing publishes, sends or spends without your approval. Check that setting before you hand Muse the write tools, because updateSheetValues and writeDoc can replace existing content. The wording of Meta's setting was not tried for this guide. In the Ryze AI chat, changes follow the chat's Tool approvals setting, which starts on Skip all approvals; Approve write & delete and Manual approve can be chosen there.
8 tool calls from the test, with what came back
The test sent 8 Google Drive calls through the Ryze AI connector on November 14, 2026. They came from Claude Code, since Muse took no part. Each was shaped so that no real file could come back: a filter nothing matches, made-up IDs, a bogus field name, a bogus page token, and values past the length cap. Nothing was listed or opened from a real Drive.
| Call | Tool | Outcome |
|---|---|---|
| Name filter matching nothing | listFiles | Succeeded with an empty result, {"files":[]}, and no paging token |
| Made-up file ID | readFile | Came back as not_found with a File not found message |
| Made-up spreadsheet ID with a two-cell range | getSheetValues | Came back as not_found |
| Same empty filter plus an unknown field | listFiles | Error 400, Invalid Value, pointing at q |
| Same empty filter plus a bogus page token | listFiles | Error 400, Invalid Value, pointing at pageToken |
| File ID with 201 characters | readFile | The connector stopped it before Google: invalid_arguments, cap of 200 |
| Filter with 501 characters | listFiles | The connector stopped it before Google: invalid_arguments, cap of 500 |
| Made-up spreadsheet ID and a blank range | getSheetValues | The connector stopped it before Google: invalid_arguments, floor of 1 |
None of the answers showed a quota counter or rate-limit header, and no limit was hit. The only numbers returned were the 200, 500 and 1 inside the three refusals.
Limits to know
These limits shape what comes back in prompts. They come from the Ryze AI help center and the tool definitions, plus Meta's description of Muse connectors.
| Limit | Detail |
|---|---|
| Reach | Tools work on picked files and Ryze AI's own files. Any other file is indistinguishable from one that does not exist. |
| Readable formats | Cell values from Sheets, plain text from Docs and Slides, content of text, CSV and JSON files. Pictures from Drive are unsupported. |
| Big or binary files | Over 10 MB, binary, or a different Google format: name only. |
| Doc output | Plain text, appended or replacing everything. No styling. |
| Rows per read | getSheetValues stops at 10,000 rows per call (tool description, November 14, 2026). Ask for the next block, for example 'Sheet1'!A10001:D20000. |
| Slow recalculation | A request timed out answer from getSheetValues means Google is still recalculating the Sheet. The tool description suggests waiting a few minutes. |
| Muse approvals | Meta says Muse does not take many important actions without approval by default. The control is in Muse Settings. |
| Muse regions | US and Canada, per Meta. |
Limits in numbers
| Limit | Number | Source |
|---|---|---|
| Drive API, per project and per user | 1,000,000 quota units a minute per project, 325,000 a minute per user per project, for Cloud projects created on or after May 1, 2026. Older projects keep earlier quotas. Which set the connector falls under was not checked | Google Drive API limits |
| Unit cost per Drive call | 5 for reads, 100 for lists, 50 for edits, 200 for downloads and exports | Google Drive API limits |
| Drive quota exceeded | 403 User rate limit exceeded, possibly 429 Rate limit exceeded; Google advises truncated exponential backoff | Google Drive API limits |
| Sheets API | Reads: 300 a minute per project, 60 per user. Writes: the same two numbers. Excess gets 429 Too many requests | Google Sheets API limits |
| Docs API | Reads 3,000 a minute per project and 300 per user; writes 600 and 60 | Google Docs API limits |
| Largest files Drive holds | Docs 1.02 million characters, Sheets 20 million cells or 100 MB, other files 5 TB | Google Drive file size limits |
| Trash retention | 30 days, then gone for good | Google Drive Trash help |
| Sheet rows per call | 10,000 for getSheetValues | Tool definition, November 14, 2026 |
| Text lengths accepted | IDs 1 to 200 characters, range 1 to 300, listFiles query 1 to 500, createFile name up to 300, createFile and writeDoc content up to 200,000 | Tool definitions, November 14, 2026 |
Sources: Google Drive API limits, Google Sheets API limits, Google Docs API limits, Google Drive file size limits, Google Drive Trash help, Ryze AI Google Drive guide. Checked November 14, 2026. Meta help: Muse connectors. Checked November 8, 2026.
First 3 prompts to run
1. Read a keyword list from a Sheet
Read the first tab of the Sheet I picked, take the keyword list in column A, and group the keywords by topic.
Tools used: getSheetValues
What comes back: The cell values of that tab, read from your own Sheet, up to 10,000 rows per call. The Sheet has to be one you picked in the Ryze AI chat or one Ryze AI created.
2. Write a report into a Google Doc
Create a new Google Doc called Weekly report and write this summary into it as plain text.
Tools used: createFile, writeDoc
What comes back: A new Doc in your Drive with a link to it. The text goes in without headings, links or formatting.
3. Add rows to a log Sheet
Append these three rows after the last row of the table in my log Sheet.
Tools used: appendSheetValues
What comes back: The rows land after the last row of the table in the Sheet you picked. Existing rows stay as they are.
Each answer comes from your own files, so this page describes what comes back instead of showing sample data. Write calls change real files, and updateSheetValues replaces the cells in the range it is given.
10 jobs to hand to Muse
Ten jobs to hand to Muse, each with the tool that does the work. 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. Meta says Muse does not take many important actions without approval by default, which covers the write jobs unless you change that setting.
| Job | What to say to Muse | Tool | On the default connection |
|---|---|---|---|
| Pull a keyword tab | Read the keywords tab of my picked Sheet and list what is in it. | getSheetValues | Yes, for picked or Ryze AI made Sheets, 10,000 rows per call |
| See what is reachable | Which Drive files can you open, newest first? | listFiles | Yes, though only picked and Ryze AI made files appear |
| Summarize a Doc | Summarize the Doc I picked. | readFile | Yes, as text |
| Summarize a deck | Give me one line per slide for the deck I picked. | readFile | Yes, as plain text |
| Describe a CSV | What columns does the CSV I picked contain? | readFile | Yes up to 10 MB; bigger or binary files return a name only |
| Draft a report as a Doc | Make a Doc and put this report in it. | createFile, then writeDoc | Yes, unstyled text |
| Extend a log | Add this week's rows under the last row of my log Sheet. | appendSheetValues | Yes, for a picked or created Sheet |
| Rewrite a block of cells | Put these values, formulas included, into A1:C10. | updateSheetValues | Yes; the range must fit the values and old cells are replaced |
| Start a fresh Sheet | Create a Sheet holding this table. | createFile, then updateSheetValues | Yes; created empty, filled by a second call, link returned |
| Store output as a file | Save this as a CSV in my Drive. | createFile | Yes, inline content up to 200,000 characters, link returned |
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 Muse to Google Drive
Three ways can give Muse your Drive files on the pages checked for this guide, and only the first is documented end to end. Meta describes custom connectors as something you ask Muse to create and never mentions a field for a server URL, so whether Muse accepts a server other than the Ryze AI one is not documented. The Ryze AI connector is the main way: one address, a Google sign-in inside Ryze AI, no Google Cloud project to set up. The others were read on their own pages on November 14, 2026, and none was tried in Muse.
| Way | Runs where | Setup in Muse | What it reaches in Drive | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI at one shared address | Ask Muse to create a custom connector for https://connector.get-ryze.ai/mcp, follow the guided setup and sign in from the link Muse sends. ryze.ai/muse offers a message to paste. Files are chosen in the Ryze AI chat | 7 tools covering listing, reading, Sheet writes, file creation and plain-text Doc writes, limited to picked and Ryze AI made files, with no delete | Free to add. Tools need an active plan or trial: Paid Ads $89 a month (7-day trial), SEO Starter $129 (3-day trial), Agency $279 |
| Google Drive MCP server by Google (untried with Muse) | Google hosts it at https://drivemcp.googleapis.com/mcp/v1, Streamable HTTP, OAuth 2.0, Developer Preview | Needs the Workspace Developer Preview Program, a Cloud project with the Drive and Drive MCP APIs enabled, a consent screen with drive.readonly and drive.file, and a Web application OAuth client marked for an AI agent. Google's pages list redirect URIs for Antigravity and Claude only, and Meta is silent on whether Muse takes such a server | 8 tools: search_files, read_file_content, list_recent_files, download_file_content, get_file_metadata and get_file_permissions read; create_file and copy_file write. It covers whatever you can open, minus files failing Google's eligibility checks. No delete, move, rename or share | Google's pages show no price; you need a Cloud project and preview access |
| Zapier MCP (untried with Muse) | Hosted by Zapier | Build an MCP URL in Zapier and enable Google Drive actions. The quickstart names Muse among its additional MCP clients and demands Streamable HTTP, and gives no Muse steps | Whichever Drive actions you switch on, such as Copy File, Delete File (Permanent), Export File, Upload File, Create Folder, Move File and Remove File Permission. No total is stated | A successful call spends 2 tasks from your Zapier plan; failed calls are free |
Options that do not fit Muse
- Claude's Google Drive connector and ChatGPT's Google Drive app. Each belongs to its own assistant and is documented only there, so neither can be added to Muse.
- Google's Sheets, Docs and Slides MCP servers. They change formatting and structure, which the Ryze AI tools cannot, yet Google's setup pages mention Antigravity and Claude and never Muse.
- Composio. Its Drive page shows steps for ChatGPT and Cursor and does not mention Muse in the pages read.
- workspace-mcp by taylorwilsdon. A Python server you run yourself with your own Google Cloud OAuth client. Muse would have to reach it at a public address, and Meta documents no such route.
- The old reference server @modelcontextprotocol/server-gdrive. npm marks it "Package no longer supported." and GitHub archived it on May 29, 2025. Google did not make it.
Which one to pick
Ryze AI is the best way to connect Muse to Google Drive when you want a chat 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 Muse. Google's own Drive server fits an agent that must read your whole Drive and a team that can run a Google Cloud project, but it is a Developer Preview that cannot edit existing files, and Meta does not document whether Muse accepts it. Zapier MCP fits a team whose Drive tasks already run through Zapier.
Sources: Google Drive MCP server, Google Drive MCP reference, Zapier MCP for Google Drive, Zapier MCP quickstart, Composio Google Drive, workspace-mcp, Reference Google Drive server, Ryze AI Google Drive guide. Checked November 14, 2026. Meta help: Muse connectors, Meta newsroom: Muse for small business, Ryze AI Muse page. Checked November 8, 2026.
Google Drive, Muse and MCP: dates that matter
| Date | What happened |
|---|---|
| November 19, 2024 | First npm release of the reference Drive server @modelcontextprotocol/server-gdrive; its last release followed on January 14, 2025 and npm now flags it deprecated. |
| May 29, 2025 | GitHub archived the repository holding that reference server, leaving it read-only. |
| April 22, 2026 | Google release notes put its Drive MCP server in Developer Preview. |
| May 1, 2026 | Google opened the Workspace MCP server to a public Developer Preview, and new Cloud projects began metering Drive in quota units. |
| May 21, 2026 | Google's Drive MCP server gained copy_file. |
| July 13, 2026 | Docs, Sheets and Slides MCP servers entered Developer Preview. |
| September 2026 | Meta launched Muse for small businesses in the US and Canada with custom connectors (newsroom post dated September 29, 2026). |
| October 1, 2026 | Google's Docs, Sheets and Slides MCP servers added comment reading and management. |
| November 11, 2026 | Google's Workspace MCP servers began turning away OAuth clients not marked as agentic. |
| November 13, 2026 | Google revised its Drive MCP file eligibility page. |
Sources: Google Workspace release notes, Workspace Updates blog, May 2026, Reference Google Drive server on npm, Reference servers repository. Checked November 14, 2026. Meta newsroom, September 2026, Ryze AI Muse page. Checked November 8, 2026.
How this guide was tested
One round of checks stands 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. Meta's pages and the Ryze AI Muse page were read on November 8, 2026.
| What was run | What came back |
|---|---|
| Tool list, November 14 | 7 google_drive tools matching the tools table: 3 read, 4 write, none that delete. |
| Empty search, November 14 | listFiles with a filter nothing matches succeeded and returned {"files":[]}. |
| Seven deliberate failures, November 14 | Each drew one of the messages in the errors table. |
| Rate limits | No quota counter or rate-limit header appeared, and no limit was hit. |
Not run for this guide: any step inside Muse. No Muse account was used, so the chat request, the guided setup, the sign-in link and Meta's approval setting follow Meta's pages and the Ryze AI Muse page as read on November 8, 2026. No real file was listed or read, so no Sheet values, Doc text or file content came back in the test. None of the 4 write tools was called, because they change files, and the Ryze AI Drive picker was not used.
Errors and fixes
Exact error messages from the test
These messages came back word for word in the test on November 14, 2026. If one of them appears in a Muse tool call, here is what it means and what to ask next.
| Message | What it means | What to do |
|---|---|---|
| File not found: <redacted>. | readFile returned not_found. Either the ID is wrong, or the file was neither picked in the Ryze AI Drive picker nor created by Ryze AI. Under drive.file those two cases look identical. | Attach the file in the Ryze AI chat via Attach files, then Upload from Drive, and retry. |
| Requested entity was not found. | getSheetValues returned not_found. The spreadsheet ID is wrong or the connection cannot reach that Sheet. | Pick the Sheet in the Ryze AI picker, or ask Muse to list files and copy the ID of a reachable Sheet. |
| Invalid Value (Error 400, location: q) | listFiles got a filter that is not valid Drive query syntax, here an unknown field. | Use a plain term such as name contains 'KPI', or drop the filter. |
| Invalid Value (Error 400, location: pageToken) | The page token was not issued by an earlier list call. The text matches the bad-filter error and only the location changes. | Restart the listing with no page token. |
| Too big: expected string to have <=200 characters | The ID passed 200 characters, so the connector refused it before reaching Google (path: fileId). A full link or extra text was likely passed as the ID. | Send just the ID portion of the link. |
| Too big: expected string to have <=500 characters | The listFiles filter passed 500 characters (path: query) and was refused before Google saw it. | Cut it down to a single name contains term. |
| Too small: expected string to have >=1 characters | The range was blank (path: range). getSheetValues wants a tab title or an A1 range; named ranges are unsupported. | Give a tab such as Sheet1 or a range such as Sheet1!A1:D50. |
Other problems
- Muse has no field for the URL
- Meta's pages describe none. Ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, or paste the message from the Ryze AI Muse page.
- The sign-in link never arrives
- Muse's guided setup was not tried for this guide. Ask Muse to send the sign-in link again, and check Settings, then Connectors, to see whether the connector was created.
- The Google Drive tools do not appear
- A tool list can be cached from before Google Drive was connected. Remove the connector in Muse under Settings, then Connectors, ask Muse to create it again, and check that the Google Drive card in Ryze AI shows Connected.
- Muse cannot see a file
- Only picked files and files Ryze AI created are visible. Pick the file in the Ryze AI chat with + > Attach files > Upload from Drive. Images, files over 10 MB and binary files come back by name only.
- Another Google account is needed
- Drive connects one Google account per workspace. Disconnect Drive in Ryze AI and connect the other account.
- A Doc write lost its formatting
- writeDoc writes plain text only. It has no headings, links or formatting, and replace mode overwrites the whole document.
- The tools say a subscription is required
- The Google Drive tools need an active Ryze AI plan or free trial. Start the trial, then retry.
- Muse is not available
- Meta says Muse is offered in the US and Canada only.
Terms on this page
- MCP
- The Model Context Protocol. The Ryze AI Muse page says the connector speaks it over HTTP with OAuth, a detail Meta's pages never mention.
- Custom connector
- Meta's term for a link to a service Muse lacks built in, created by asking Muse in a chat.
- Secure Credentials Store
- Where Meta says Muse keeps a connector's credentials.
- drive.file
- A Google permission that confines an app to files a user opens with it or shares through a picker, plus files the app makes.
- Google Picker
- Google's Drive file-open dialog. In Ryze AI it appears in the chat composer under + > Attach files > Upload from Drive.
- File ID
- The string inside a file's link that names it. The tools take it in place of a file name, and Google says spreadsheet IDs survive renames.
- A1 notation
- How Sheets names cells: tab, then column letters and row numbers. Google's example: Sheet1!A1:B2 is the first two rows and columns of Sheet1.
Sources: Meta help: Muse connectors, Meta newsroom: Muse for small business. Checked November 8, 2026. Google Picker overview, Google Drive scopes, Google Sheets concepts. Checked November 14, 2026.
Frequently asked questions
How do I connect Muse to Google Drive?
Connect Google Drive in a Ryze AI workspace, pick your files in the Ryze AI chat, then ask Muse in a chat to create a custom connector for https://connector.get-ryze.ai/mcp, follow the guided setup and sign in to Ryze AI from the link Muse sends.
Is there a Google Drive connector for Muse?
Yes: ask Muse to create a custom connector for the Ryze AI address and Muse gets 7 Google Drive tools. Google's own Drive MCP server is a Developer Preview whose setup pages name Antigravity and Claude, and Zapier's quickstart lists Muse among its MCP clients.
Is there a Google Drive MCP for Muse?
The Ryze AI connector is the documented route. Google hosts its own Drive MCP server at https://drivemcp.googleapis.com/mcp/v1, but Google's pages give no Muse steps and Meta does not say whether Muse accepts a server you set up yourself.
What is a Google Drive MCP server?
A server that lets an AI client such as Muse 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.
Where is Muse available, and which plan do I need?
Meta says Muse is available in the US and Canada. Its help and newsroom pages reviewed name no plan for custom connectors, so no plan requirement is stated here.
Is there a field for the server URL in Muse?
Meta's pages describe none. Custom connectors are created by asking Muse in a chat, and Muse starts a guided setup. The Ryze AI page at ryze.ai/muse has a ready-made message to paste.
Does Meta review custom connectors?
No. Meta says it does not review custom connectors or how they use data, and that Muse stores the credentials in its Secure Credentials Store. Review what the Ryze AI connection can do in Drive before you allow it.
Can Muse 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 Muse 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 Muse delete Drive files?
No. The connector has no delete tool. Google's drive.file scope covers deleting an app's own files, but Ryze AI exposes no tool that does it.
Does Muse ask before it changes my files?
Meta says by default Muse does not take many important actions without approval, and its newsroom says nothing publishes, sends or spends without your approval. You change the approval behavior in Settings. This was not tried for this guide, so check the setting before you hand Muse the write tools.
Can Muse read a PDF or an image from Drive?
No. Images picked from Drive are not supported, and binary files, files over 10 MB and Google formats other than Sheets, Docs and Slides are attached by name only.
Can I use 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 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?
Manage or disconnect the connector in Muse under Settings, then Connectors. You can also disconnect Google Drive on its card in Ryze AI, or remove the access on your Google Account permissions page.