Those four operations cover almost everything a spreadsheet task needs, and batching keeps a multi-range change from becoming several round trips. The Google Cloud OAuth setup is the only real work: a project, a consent screen and a desktop client ID before the first call.
A server over the Google Sheets API covering the operations a spreadsheet task actually needs: create a spreadsheet, read a range, write a range, append rows, clear, read metadata, and batch several updates into one request.
- A new spreadsheet created with custom sheet names, returning its ID and URL
- Any range read back as a 2D array of cell values
- A range written, overwriting what was there, with update statistics returned
- Rows appended to the end of an existing range
- A range cleared
- Spreadsheet metadata: title, URL, sheet information and dimensions
- Several range updates sent as one request
A Google Cloud project with the Google Sheets API enabled, an OAuth consent screen, and Desktop Application OAuth client credentials downloaded as JSON. The scope is `https://www.googleapis.com/auth/spreadsheets`, and the credentials file path goes into the server config.