Google Sheets
Put the reporting where someone already reads it
Every other mount is a place your agent reads from or changes. This one is a destination: instead of pasting a table into chat where it dies, the agent writes the numbers into a spreadsheet your team already has open — on the same Google connection, under the same gate.
$ claude mcp add --transport http sheets \
https://mcp.getducto.com/sheets
✓ connected — 7 tools
read-only until you set a policy
What your agent does here
Real Google Sheets work, in conversation
Read a sheet without reading the whole file
Tab names and sizes come back separately from cell values, so an agent can find the right range before pulling any data into its context.
sheets_get_spreadsheetsheets_read_valuessheets_status
Create the report and append to it
Create a spreadsheet with named tabs, then append rows to the end of a range — additive, so a weekly run never overwrites last week.
sheets_create_spreadsheetsheets_append_values
Overwrite or clear a range deliberately
Updating a range replaces what is there; clearing one empties it. Both are separate tools with separate gates, because they are separate decisions.
sheets_update_valuessheets_clear_values
Governed writes
How writes are enforced
Writing rows is the one thing agents own outright — nothing here spends money or reaches a customer, and the sheet's own version history is the undo. Clearing a range is blocked by default: the API tells you which range it emptied and never what was in it.
The full request path is on the security architecture page.
Tool reference
Every tool in the sheets mount
Generated from the running gateway's tool registry — this is the complete list, not a highlight reel.