Cursor is excellent on a folder of files and has nothing to say about a grid in a browser tab. So the sheet that needs a judgment call on four thousand rows, sort the free-text notes into six categories, normalize every company name, stays out of reach. The options are a Sheets API script that does exactly what you spelled out, or an afternoon of copy and paste.
Scratch pulls the tab down, one local record per row. Cursor edits the fields on your laptop; Scratch shows each cell as a diff; it writes only the cells you approve. The cells nobody touched keep their values and their number formats, so a bad pass costs you nothing.
How it works
- Scratch pulls your tabs into files. Sign in with Google and paste the URL of each spreadsheet Scratch may touch. Every tab becomes a table, row 1 becomes the field names, and a managed
Scratch IDcolumn in position A carries row identity so a sort cannot scramble it. - Cursor edits the rows. Open the folder in Cursor. Cmd+K a few rows to settle the prompt, then turn on Agent mode for the tab. Sort every note into one of these six categories and leave the rest of the row alone. Cursor works the files, never the live sheet.
- You review every diff and publish. Scratch shows each changed cell beside its original value. Approve what holds up, and Scratch writes only those cells through the Sheets API.
What people use it for
The data passes that turn into scripts because the grid only does find-and-replace:
- Sort a column of free-text notes into the dropdown categories you report on.
- Normalize company names, job titles, industries, and country codes across a whole export.
- Rewrite a product or content column for the entire catalog in one reviewed batch.
- Fill blank cells from what the rest of the row already says.
- Flag and merge duplicates that three people created in three styles.
Run it on 50 rows to feel the loop, then turn Agent mode loose on the tab.
Why not a Sheets MCP server?
An MCP server, or a script with the Sheets API, gives Cursor a live write path into the spreadsheet. Every edit lands in the cell immediately, with no diff, no batch, and nothing to reject. Across four thousand rows, one confident pass is the whole sheet, and version history is your only undo.
Scratch gives Cursor the same full read and write access, but against a local copy, and pulls the publish step out for you. Agent mode can change any cell; only you commit it. Every published change is reversible per row.
What Cursor edits in Google Sheets
- Text, number, checkbox, and dropdown columns
- Dates, datetimes, currency, and percentages, as typed values rather than strings
- New rows, appended below your data
- Row deletions, applied bottom-up so the rows above never shift underneath
Field names come from row 1: reordering columns keeps the field, renaming a header creates a new one, and empty-headered columns are invisible to Scratch. Cells hold scalars, so a list or object fails the publish loudly instead of being stringified. For the full picture, see Scratch for Google Sheets.
Questions people ask
Which spreadsheets can it reach?
Only the ones whose URLs you pasted. The OAuth scope is exactly spreadsheets with no Drive scope, so Scratch cannot enumerate your files, browse folders, open a spreadsheet you did not hand it, or delete anything. Edit the list later from Edit Connection.
Does it clobber formatting or untouched columns?
No. Writes are per cell, so anything nobody approved keeps its value and its number format. Validation, checkboxes, and date formats stay as you set them.
What is the Scratch ID column for?
Row identity. Row position is not stable under a sort, so Scratch manages one column headed Scratch ID in position A and stamps a short id into it, identified by developer metadata so it survives reorders. Delete or move it and the pull stops with an error and a recovery recipe rather than guessing which row is which.
Can Agent mode run the whole tab?
Yes, that is the use case. Cmd+K a handful of rows to settle the prompt, then let Agent mode work the tab. Reading local files instead of paging an API is what makes a few thousand rows practical in one pass.
Can I roll a change back after it publishes?
Yes, per row. Every published change is reversible from Scratch, and the original value sits beside the rewrite until you pick one.
How do I watch it run on my own sheet first?
Pull one tab, run the prompt on 50 rows, and read the diff before anything publishes. Nothing reaches Google until you approve it.
See it on your own sheet
Book a 30-minute demo on your own spreadsheet →, or try Scratch free and run the first pass yourself.