How to Make Claude Edit Google Sheets

Claude can edit Google Sheets through three practical routes: a direct connection via an MCP server that talks to the Sheets API, a Google Apps Script that Claude writes and you run inside the sheet, or a copy-paste loop where Claude supplies values or formulas and you apply them. The right route depends on how much direct access you want to give Claude and how often you'll repeat the task.

Before choosing, think about access controls. A direct connection lets Claude read and write without a manual step, which is efficient but requires you to grant it the right permissions on the sheet. An Apps Script sits in between: Claude writes the code, but you review and run it. Tools like fenbs let you keep approved instructions and calculation decisions in one place so Claude applies the right logic every time, even across sessions.

Route 1: The Google Sheets MCP server

The Google Sheets MCP server gives Claude direct read and write access to your spreadsheets through Google's API. Once it's connected, Claude can call tools to read cell ranges, write values, create or rename sheets, and more — all within a single conversation.

To set it up, add the Google Sheets MCP server to Claude's configuration and authenticate with your Google account when prompted. The sign-in uses OAuth, so you approve the scopes (typically reading and writing spreadsheets) in a browser window. You'll find setup instructions in the Google Sheets MCP guide.

After connecting, Claude can edit sheets by name or by spreadsheet ID. It reads a range, makes a change, and writes it back. You can ask it to update a formula, reformat a column, append new rows, or reorganize data. Because each action is a real API call, changes appear in the sheet immediately.

One thing to check: the OAuth scopes you approve determine what Claude can do. If you grant read-only access, Claude can read but can't write. Review the requested permissions before approving, and revoke access from Google's security settings↗ (opens in a new tab) if you no longer need the connection.

Route 2: A Google Apps Script written by Claude

Apps Script runs inside Google Workspace with full access to the spreadsheet that hosts it. You can ask Claude to write a script that performs any edit — sorting rows, applying conditional formatting, filling in calculated values — and then paste that script into the Apps Script editor in your sheet.

This approach keeps Claude out of your sheet directly. Claude generates code that you review before running. If the logic is complex, you can test it on a copy of the sheet first. The main downside is that you have to copy, paste and run the script yourself, which adds friction for repeated tasks.

To use Apps Script: in your Google Sheet, go to Extensions → Apps Script, paste Claude's generated code into the editor, and run the function. Google may ask you to authorize the script to access your sheet on the first run.

Route 3: Copy-paste with Claude

The simplest route needs no configuration. Copy the data from your sheet, paste it into the conversation, and ask Claude to transform it, write a formula, or suggest corrections. Then paste the result back into the sheet yourself.

This works well for one-off tasks: writing a complex VLOOKUP, reformatting a messy date column, or spot-checking a formula. It does not work well for large datasets (pasting many thousands of rows into a conversation is unwieldy) or for tasks that need to run on a regular schedule.

Checking changes after Claude edits the sheet

After any direct edit — whether through MCP or a script — check that the changes are correct before relying on them. Google Sheets keeps a full version history: go to File → Version history → See version history to compare the sheet before and after. For formulas, review the formula bar rather than just the displayed value.

If Claude applies a formula across many rows, spot-check several cells rather than just the first one. Edge cases — blank cells, differently formatted dates, text where a number is expected — can produce silent errors in formulas that appear correct until a specific row triggers them.

For edits to sheets others rely on, consider making changes on a duplicate first. Once you've confirmed the result looks right, apply the same change to the live sheet. This is true regardless of whether the edit came from Claude or a human.

Access controls to review

A direct Google Sheets connection carries real permissions. Review these before and after setup.

• OAuth scopes: read-only vs. read-write. Grant the minimum access the task requires.
• Sheet sharing: the connection uses your Google account, so it can access any sheet your account can access. Keep that in mind for sheets with sensitive data.
• Revocation: if you stop using the connection, revoke it at Google's security settings page so access doesn't persist.
• Service accounts: teams that connect Claude to shared sheets often use a Google service account with its own limited permissions, rather than a personal account.

How to do this with fenbs

1. Create a free account and add a project for the work the sheet supports.
2. Add a Decision or rule for each agreed calculation, column definition, or transformation rule. Give each one the person who decided it and the reason.
3. Connect Claude to fenbs via Integrations and to Google Sheets via the MCP server setup guide at Google Sheets MCP.
4. At the start of a session, ask Claude to read the project context from fenbs. It retrieves the Decisions and rules before it touches the sheet.
5. After Claude edits the sheet, check the changes in Google Sheets' version history and save any new decisions in fenbs for the next session.

For related topics, see Claude for Sheets for the Claude-specific integration approach, and what is Claude AI for an overview of Claude's capabilities.