gdrive_read_file
Read contents of a file from Google Drive
Find a file in Google Drive, read it, and read ranges or update a single cell in a Google Sheet without opening either one.
LABSCO SUMMARY
Three of the four tools read and the fourth writes a single cell by range and value, which keeps an agent's edits small enough to check rather than letting it replace a sheet wholesale. Everything begins at gdrive_search, since the read and write tools address files by ID — a session that cannot find the file cannot do anything else with it.
A four-tool server over Google Drive and Google Sheets: search and read for files, range reads and single-cell writes for spreadsheets.
CLIENT_ID, CLIENT_SECRET and GDRIVE_CREDS_DIR — a Google client credential pair and a directory the server keeps its credentials in — plus a Drive account holding the files you mean to reach.
One command plus credentials — npx -y @isaacphi/mcp-gdrive, then supply credentials
USE CASES
Find the spreadsheet by name, then read the ranges that matter with control over how the values and formatting come back.
Locate the sheet, then set one cell by range and value. Single-cell writes keep an agent's edits small enough to review in the same message that made them.
Search finds the file and returns its ID; the read tool returns its contents, so a document mentioned in passing can be quoted accurately instead of remembered.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
gdrive_read_fileRead contents of a file from Google Drive
gdrive_searchSearch for files in Google Drive
gsheets_readRead data from a Google Spreadsheet with flexible options for ranges and formatting
gsheets_update_cellUpdate a cell value in a Google Spreadsheet
BEFORE YOU INSTALL
4 tools when we connected. Three tools only read; gsheets_update_cell writes to a real spreadsheet. Drive access is read-only, so nothing can upload, rename or delete a Drive file.
The documented client runs the server on your machine.
CONTEXT COST
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npx -y @isaacphi/mcp-gdrive{
"mcpServers": {
"gdrive": {
"command": "npx",
"args": [
"-y",
"@isaacphi/mcp-gdrive"
],
"env": {
"CLIENT_ID": "<YOUR_CLIENT_ID>",
"CLIENT_SECRET": "<YOUR_CLIENT_SECRET>",
"GDRIVE_CREDS_DIR": "<YOUR_GDRIVE_CREDS_DIR>"
}
}
}
}