Connect Claude to Google Sheets in 60 Seconds (Full Walkthrough)

To connect Claude to Google Sheets, you don't need a Google Cloud project, an API key, or a weekend. With SheetsGate it's: sign in with Google → grant the sheets you choose → copy your MCP Endpoint URL → paste it into Claude. From that moment, Claude reads and writes your real spreadsheets in plain English.

This is the full walkthrough — every step, what you'll see on screen, and the first prompts to run once you're live.

Step 1: Sign in and grant your sheets (30 seconds)

Go to sheetsgate.com and sign in with your Google account. You'll be asked to grant access — and here's the detail worth noticing: SheetsGate uses Google's drive.file scope, which means you pick exactly which spreadsheets it can see. Not your Drive. Not your email. Just the sheets you select.

Choose the spreadsheets you want Claude working with. You can add or remove files any time from the dashboard — access changes take effect immediately.

Step 2: Create your connection token (15 seconds)

In your dashboard, open Connections and create a token. Give it a label you'll recognize later — "Claude Desktop", "Work laptop", whatever. The dashboard hands you your MCP Endpoint URL, with a copy button:

https://…/mcp/<your-token>   ← shown in full in your dashboard, with a copy button

That URL is the integration. One line, no JSON key files, no environment variables.

Pro tip: on paid plans you get multiple tokens — create one per tool (Claude, Cursor, n8n). Each can be restricted to different files and revoked independently, so if you ever stop trusting one tool, you kill one token and nothing else breaks.

Step 3: Paste it into Claude (15 seconds)

Claude (claude.ai or Desktop) via connectors: Settings → Connectors → Add custom connector → paste your endpoint URL. Done.

Other clients and config files: your dashboard's connection panel shows ready-made snippets — an mcpServers config block for clients configured by file (Cursor, Windsurf, VS Code), plus curl, Python, and Node examples. That last part is worth noticing: the same endpoint answers plain JSON-RPC, so scripts can use your sheets tools with no MCP client at all.

One URL, every tool — MCP is an open standard, so you set this up once and Claude, Cursor, and n8n all share it.

Step 4: Your first five prompts

Claude now has real spreadsheet tools. Start here:

1. "What spreadsheets can you see?" — Claude lists your granted files. Instant confirmation everything's wired up.
2. "Read the first 20 rows of [your sheet] and describe what this data is." — watch it pull live data, no pasting.
3. "Append a test row to [sheet] with today's date and the note 'connected via SheetsGate'." — your first AI write. Go look at the sheet; it's there.
4. "Summarize this week's numbers from [sheet] as three bullet points for my team." — the workflow that pays for itself every Monday.
5. "Give me a map of [sheet]: every tab, its size, and what's in the header row of each." — Claude explores the file's structure on its own, which is what makes everything after this feel effortless.

All five run on the free tier. From there it compounds — cleanups ("standardize all the phone numbers"), analysis ("which region is behind target?") — and paid tiers unlock the power tools: creating spreadsheets, writing formulas, find & replace, formatting, charts.

What you'll see in your dashboard

This is the part a config file never gives you:

• Usage per token — every call Claude makes: which tool, when, how fast, success or failure. If Claude did something, you can see it.
• Token controls — restrict a token to specific files, or revoke it in one click. Claude is told the names of files it's restricted to, not just opaque IDs — so it's much harder for it to reach for the wrong spreadsheet.
• Workspaces — set standing instructions once ("Amounts in USD, FY starts April, never touch column A") and pin your key files. Every Claude session starts already knowing your rules — no more re-explaining your spreadsheet's quirks in every chat.

If something doesn't work

Honest troubleshooting, though the list is short by design:

• Claude can't see a spreadsheet → it's not granted yet. Add it in your SheetsGate dashboard; access is immediate.
• Tools don't appear in Claude Desktop (config-file route) → fully quit and restart Claude Desktop; the config is read at startup.
• A write was rejected → check the token's file restrictions in Connections — that's usually the guardrail doing its job.

Compare that with the self-hosted route, where troubleshooting means Google Cloud Console, OAuth consent screens, expired refresh tokens, and per-machine config drift. (If you want full control and your own infrastructure, self-hosting an open-source MCP server is a legitimate path — it's just a different hobby.)

Frequently asked questions

Do I need a paid Claude plan?

Local MCP servers work with Claude Desktop broadly; remote connectors availability varies by Claude plan — check Anthropic's current docs. The SheetsGate side works the same either way, and SheetsGate itself has a free tier.

Does this work on multiple computers?

Yes — that's a core advantage of a hosted endpoint. The same URL works from your desktop, laptop, and claude.ai in the browser. Nothing to reinstall per machine.

Can I limit Claude to read-only or to specific files?

Yes. Token permissions (paid plans) include a read-only mode that disables all write tools server-side, file restrictions that limit which spreadsheets a token can touch, and column protections for columns Claude must never modify. Destructive operations ask for confirmation first in clients that support it.

What happens to my Google credentials?

They stay on SheetsGate's servers, AES-256-GCM encrypted at rest — they never appear in any config file on your machine. Claude only ever holds its scoped SheetsGate token (stored server-side as a bcrypt hash), which you can revoke anytime.

---

Ready? Connect your first sheet free — no card, about a minute. Then see what your AI can actually do with it →