Issued with creating google sheet (403 error for storage quota )

[kkumargitkk]

Able to list sheets and update sheets
But creating sheet throws 403 error mentioning no storage etc
But I have 15 gb available and able to create sheet manually
The folder I created has been shared with service acct email with editor access
I am able to update existing sheets

[Yikizi]

same issue here

[wentaoyan-code]

same issue

[xing5]

This is usually a permission issue where the account that operates google sheets requires certain google drive access.

Make sure you are using the latest version and check out if this discussion helps #24

[anakornk]

same issue here

[Dreampip]

same issue here

[Marufakamallabonno]

This is probably because - service accounts may have effectively zero or limited usable storage quota, independent from the human account’s quota. Some new service accounts are being given “0 bytes” storage quota by default, so attempts to create new files fail with that 403.

Even if your account quota is fine, the service account’s own “Drive space” might already be “full” (or assigned zero) under Google’s internal policies.
(https://community.latenode.com/t/service-account-cannot-retrieve-drive-storage-quota-information/32158)

[jcheek]

I had this too, and I was able to fix it by ensuring the Drive Folder ID (DRIVE_FOLDER_ID) was a folder ON A SHARED DRIVE to which the service account had write access. Then the service can create spreadsheets, but only in the root of that folder. When using a service account, that service account doesn't get access to your own account's Google Drive storage or inherit access to your Google Drive. You have to use OAuth to give it access to create in your own storage ("My Drive").

A service account does, however, get access to your org's Shared Drive storage, so if you are using this on behalf of an org that has shared storage, create a folder on the shared drive, give that service account write access to that folder, and use that Drive Folder ID in your MCP config.

Or if you are just using it for your own personal use, choose to authenticate via OAuth. It will require you to sign in via the browser, but the MCP server will inherit your permissions (and access to your Google Drive storage and quotas, etc.)

BTW, the docs don't ever say how to get the Drive Folder ID. Fortunately my AI knew and told me. if you are browsing Google Drive in a web browser, you will have a URL like drive.google.com/drive/folders/abc123. That abc123 is your Drive Folder ID.

I want to give my AI the ability to create spreadsheets in subfolders, so I'm looking for an easy way to do that. I'll see what I can find.

[jcheek]

looking at the forks, it looks like https://github.com/lukmanr/mcp-google-sheets has already implemented the ability to create spreadsheets other than the root, and also added the ability to list folders so that the MCP server can find the folder ID to place it in a folder other than the root. Unforch his fork is one commit behind, so I'll see if I can fork and pull in his changes.

[jcheek]

ok I updated my fork. https://github.com/ziquid/mcp-google-sheets or just run it with uvx --from git+https://github.com/ziquid/mcp-google-sheets.git mcp-google-sheets

[xing5]

Thanks for the feedback, if you have time can you create a pull request?

[jcheek]

all i did was add code from others. the bulk of the code came from @lukmanr. It is MIT-licensed, but I think it would be proper to ask him if we could merge his code back into your main fork rather than just take it. Although, I did just take it for my fork... anyway, let me send him a note first and ask if he minds. Hopefully he'll have no issue with it.

[lukmanr]

I raised PR #48 with my changes - thanks!