mcp-google-sheets
MCP server for Google Sheets and Google Drive: an agent reads, edits and creates spreadsheets, tabs and charts
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Writes and changes data in your Google Sheets and Google Drive
- Can grant spreadsheet access to other users by email
- Handles service account keys or OAuth credentials
Install
Manual install
uvx mcp-google-sheets@latestSet SERVICE_ACCOUNT_PATH and DRIVE_FOLDER_ID before running. Requires uv installed.
This is third-party code. Review the repository files before installing.
What it does
The server links an MCP client to the Google Sheets and Google Drive APIs. The agent finds spreadsheets in a Drive folder, reads ranges in A1 notation, writes and batch-updates cells, inserts rows and columns, and creates tabs and whole spreadsheets. It also reads formulas, copies and renames sheets, builds charts and shares files by email. To save context you can expose only the tools you need via ENABLED_TOOLS or the include-tools flag.
Who it is for. For analysts, marketers and business owners who keep records and reports in Google Sheets.
Good fit when
- You want an agent to read and update Google Sheets data
- You need a report or summary across several spreadsheets
- You want to create a spreadsheet, tab or chart without manual work
Not a fit when
- You have no Google Cloud project with a service account or OAuth
- You need local Excel files rather than Google cloud
Example request
Build a per-manager summary from the quarterly sales sheet and write it to a new tabLimitations
It needs a Google Cloud project with the Google Sheets API and Google Drive API enabled and one auth method: service account, OAuth or a base64 key. For a service account you must share the Drive folder with its email. The server works with Google cloud spreadsheets and does not open local Excel files.
How to disable. Remove the mcp-google-sheets block from your MCP client config and restart it. No separate uninstall is needed because uvx runs the package on demand.
MCP
- Transport
- stdio, sse
- Authentication
- OAuth
| Environment variables | |
|---|---|
| SERVICE_ACCOUNT_PATH secret | Path to the Google Cloud service account JSON key |
| DRIVE_FOLDER_ID | Id of the Google Drive folder shared with the service account |
| CREDENTIALS_PATH secret | Path to the OAuth client file for browser login |
| CREDENTIALS_CONFIG secret | Base64 credentials content instead of a file on disk |
Security check
- Writes and changes data in your Google Sheets and Google Drive
- Can grant spreadsheet access to other users by email
- Handles service account keys or OAuth credentials
README in short
The README covers a one-line uvx launch, four Google Cloud auth methods and detailed service account and OAuth setup. It lists every tool for reading, writing, batch updates, sheet operations, charts and sharing. It shows Claude Desktop configs and a Docker run with SSE transport. Tool filtering for context savings is documented separately. MIT licensed.
FAQ
Which auth method should I pick?
For server automation a service account is recommended because it works without a browser. For personal use OAuth with a browser login on first run is fine.
How do I reduce context usage?
All tools are enabled by default. Use the ENABLED_TOOLS variable or the include-tools flag to keep only what you need, for example reading and writing data.
Related
166 skills for scientific work: bioinformatics, cheminformatics, clinical data, geospatial analysis and 100+ databases
Google's open-source MCP server for databases: ready tools for Postgres, MySQL, BigQuery, Spanner and more, plus custom tools in tools.yaml
Official Hugging Face skills: Hub operations via the hf CLI, datasets, model training, Spaces, evals and deployment
A visualization language for agents and an MCP server: neat charts from a simple semantic spec