read_cellLABSCO SUMMARY
A sheet you can read and write without wiring up Google OAuth.
The Apps Script deployment does the authenticating, which is what makes setup short and also what concentrates everything into one URL. Good for your own workbook, provided you treat that URL the way you treat a password.
What it is
A Python MCP server that talks to a Google Apps Script Web App you deploy yourself. The script runs under your own Google session, so the sheet is reached without handing OAuth credentials or tokens to the server.
What you get
- Single cells and whole ranges read back from a sheet
- Values written to one cell or across a range
- A range cleared
- The sheets in the workbook listed by name
- A connection test that says whether the Apps Script side is answering
Requirements
Python 3.8+, a Google account with access to Sheets and Apps Script, and a Web App deployment whose /exec URL goes in APPS_SCRIPT_URL. That deployment publishes with execute-as-you and access-for-anyone, so whoever holds the URL can read and write the sheet: keep it out of commits, and for anything past testing make the Apps Script require a shared secret parameter.
Setup effort
Build from source — git clone https://github.com/jona-mhw/google-sheets-mcp.git
USE CASES
01
Pulling a few numbers out of a spreadsheet mid-conversation
Read the cell or the range you mean and carry on, without opening the file.
02
Writing results back where colleagues will look for them
Put a worked-out figure into a cell, or a block of values across a range.
03
Finding your way around a workbook somebody else built
List the sheets by name, then read the range that looks like the one you want.
04
Resetting a scratch area before the next run
Clear the old range, then write the new values into it.
05
Telling an empty answer apart from a broken connection
Run the connection test — the Apps Script side either answers or it does not.
7 tools
Listed in project docs. Your client may show a different list.
write_cellread_rangewrite_rangeclear_rangelist_sheetstest_connectionBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- Python 3.8+
- A Google account with access to Sheets and Apps Script
- APPS_SCRIPT_URL in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/jona-mhw/google-sheets-mcp.git
cd google-sheets-mcp/mcp-server
pip install -r requirements.txtAt script.google.com, create a new project and paste in the contents of apps-script/Code.gs from your clone
Deploy → New deployment → Web app, with Execute as: Me and Who has access: Anyone
Copy the URL that ends in /exec: that is your APPS_SCRIPT_URL. Anyone who has it can read and write the sheet, so keep it private
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"google-sheets": {
"command": "python",
"args": [
"server.py"
],
"cwd": "<YOUR_PATH_TO_GOOGLE_SHEETS_MCP_SERVER>",
"env": {
"APPS_SCRIPT_URL": "https://script.google.com/macros/s/<YOUR_SCRIPT_ID>/exec",
"DEBUG": "false"
}
}
}
}<YOUR_PATH_TO_GOOGLE_SHEETS_MCP_SERVER> (Spanish for /absolute/path/to/…) is the full path of the mcp-server folder in your clone, and https://script.google.com/macros/s/<YOUR_SCRIPT_ID>/exec is the /exec URL from the Apps Script step. "cwd" must be an absolute path. Restart the client afterwards.
