Connect Google Sheets to Claude Code

Let Claude append rows and update cells directly in Google Sheets. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Google Sheets to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Google Sheets, you add a Google Sheets MCP server: a small hosted service that exposes Google Sheets's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Google Sheets account. No API keys pasted into config files.

claude mcp add --transport http google-sheets https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Google Sheets once connected?

Full read-write Google Sheets access lets Claude append rows, update specific cells or ranges, add and rename tabs, and write formulas back into the grid. The data wrangling that used to mean exporting, editing, and re-pasting happens directly in the spreadsheet your team already shares.

Append new rows to a tracker tab with mapped column values
Update specific cells or a named range without touching the rest
Add, rename, or clear a tab in an existing spreadsheet
Write a formula into a cell and let the sheet compute it
Find rows matching a query and update them in place
Format a range so a report reads cleanly before you share it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Google Sheets access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Google Sheets API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Google Sheets changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Google Sheets connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Google Sheets connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Google Sheets account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Google Sheets's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Google Sheets?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Google Sheets account it signs in with. Revoking access is one click in Google Sheets.

More on the Google Sheets connector

Google Sheets connector for claude.ai Airtable + Claude Code PostgreSQL + Claude Code MySQL + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us