Manages sheets stored in the user's personal Google Drive, leveraging Drive API for file ownership and sharing.
Creates and reads Google Sheets owned by the authenticated user, with OAuth-based access for personal Drive.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
OAuth-based Google Sheets MCP. Files are owned by you (the authenticated user), not a service account, so they land in your personal Drive and ownership/sharing works the normal way.
Companion to mcp-studio-google-sheets-mcp
which uses a service account. The OAuth flavour avoids the
"service-accounts-in-personal-projects can't create files" landmine.
You need a Google OAuth Client ID before installing.
https://console.cloud.google.com → APIs & Services → Credentials.
Create Credentials → OAuth client ID.
Application type: Desktop app. (Web app works too if you prefer.)
Give it a name (e.g. "MCP Studio Sheets"). Click Create.
Copy the Client ID Google shows you. (No client secret needed — Studio uses PKCE.)
On the OAuth consent screen tab, add your Google email to Test users if the consent screen is in Testing mode.
Make sure Google Sheets API and Google Drive API are enabled (APIs & Services → Library → Enable).
Related MCP server: Google Sheets MCP Server
/install https://github.com/RPieterse/mcp-studio-google-sheets-oauth-mcpAfter install, Studio opens Settings → MCP Servers → Google Sheets (OAuth). Expand the row, then:
Paste your OAuth Client ID into the input field and click Save.
Click Authorize in browser below. Approve the Google consent screen. Studio captures the tokens.
After that:
/osheet_create Demo creates a sheet owned by you, in your My Drive.
The service-account MCP uses /sheet_create, /sheet_read. This OAuth
flavour uses /osheet_create, /osheet_read so you can have BOTH MCPs
installed at the same time without trigger collisions.
Studio currently keeps OAuth tokens in memory only (no keychain
persistence yet — tracked in the main repo's docs/ROADMAP.md). You'll
re-authorize on every Studio launch.
Google access tokens expire after ~1 hour. The MCP's OAuth2Client
auto-refreshes IF Google handed us a refresh_token on first consent.
If it didn't (this happens when you've authorized this client before),
reauthorize with prompt=consent once to force a new refresh token.
This server cannot be deployed
Permissioned access to Gmail, Drive and Calendar via the user's own Google account
Read and write Google Sheets with your own service account: list tabs, read, append, update, export.
Google Docs MCP Pack — read, create, and edit Google Docs via OAuth. Reuses the google_sheets…
Google Sheets via Apify: write Apify datasets or JSON rows to a sheet, or read a sheet as JSON.