Google Sheets MCP server

google-sheets-mcp

Google Sheets as MCP tools. Read and write ranges without destroying the formulas underneath.

A single Go binary that speaks MCP over stdio. It runs as a subprocess of your client, on your own machine, against your own Google account. There is no server to host, no shared deployment and no service account: you create a Google OAuth client, log in once, and the refresh token stays in your OS keyring.

It works inside a spreadsheet. Finding, sharing, moving and trashing files, and their comment threads and revisions, belong to a server built on the Drive API. A cell note is a Sheets field and is here.

Why google-sheets-mcp

A spreadsheet has no undo behind an API call, and the value you can see is rarely the whole cell: underneath it there may be a formula, a different stored type, or a note. So the writes here are guarded rather than trusting. writevalues reads the target first and refuses to overwrite anything non-empty without overwrite, or a formula without overwriteformulas as well, naming the cells each time; every value Google's parser changes on the way in is reported back to you.

It also does the index arithmetic. Ranges are A1 throughout, sheet titles are quoted for you — Google names the first sheet in the account's language, so it is often not an English word — and the one place A1 turns into a GridRange is a single package.

It works inside a spreadsheet. Finding, sharing, moving and trashing files, and their comment threads and revisions, belong to a server built on the Drive API. A cell note is a Sheets field and is here.

Reading, writing, formatting, the objects attached to a range, gsheets:// resources, durable anchors, charts, pivot tables and Connected Sheets data sources all work. The twenty-one tools and their arguments are stable: a breaking change needs a major version, and a gate compares every commit against the last tag. It has been driven by one MCP client, which is what to know before trusting it in a second. The history is §16 of docs/architecture.md.

Install

go install github.com/mmedum/google-sheets-mcp/cmd/google-sheets-mcp@latest

Or take an archive from the latest release — Linux, macOS and Windows, on amd64 and arm64 — and verify it before you run it:

sha256sum -c checksums.txt --ignore-missing

# The checksum file is signed with a keyless Sigstore certificate tied to
# the release workflow's identity. The bundle carries both.
cosign verify-blob checksums.txt \
  --bundle checksums.txt.bundle \
  --certificate-identity-regexp 'https://github\.com/mmedum/google-sheets-mcp/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# And the archive itself carries build provenance.
gh attestation verify google-sheets-mcp_*.tar.gz --repo mmedum/google-sheets-mcp

Every archive also ships an SBOM, so you can see what is inside a binary you did not build. Builds are reproducible: -trimpath, and the commit's timestamp rather than the build's, so rebuilding a tag gives the same bytes.

Claude Desktop

Shortened. The full README is on GitHub.