Model or dataset
xing5/mcp-google-sheets avatar
xing5/mcp-google-sheets

mcp-google-sheets exposes 19 tools, costs 13,000 tokens before you type, and tells you to run it unpinned

This MCP server integrates with your Google Drive and Google Sheets, to enable creating and modifying spreadsheets.

1,020 stars253 forksPythonMIT

At a glance

What is it?
This is a Python MCP server that puts the Sheets and Drive APIs behind a tool list for any compatible client, launched in one line with the uv package runner. Two details in its own documentation shape how you should read it. The credential is a service account key file pointed at by an environment variable, and every documented invocation ends with a tag that means resolve the newest release from the index, which the page recommends as best practice.
Who is it for?
Use this if you want an agent writing to a spreadsheet folder you already scoped, and enable tool filtering before the first conversation so the context cost is a few hundred tokens rather than thirteen thousand. Two things to settle first.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 6 months ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • xing5/mcp-google-sheets1,020 ★ · +22
Star history
Repository2026-09-112026-11-15
xing5/mcp-google-sheets9981k

22 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Every documented command resolves the newest release at launch

The quick start is one line, and it is repeated three times in the page for emphasis:

bash
uvx mcp-google-sheets@latest

The stated reason is that without the tag the runner may use a cached older version, so the advice is to always append it. That advice appears in the prose, in a callout labelled as a tip, and again inside both example client configurations. It is a reasonable default for a tool people install casually, and it is also the opposite of pinning: each launch re-resolves the package from the index, so the code your agent executes can differ between two launches an hour apart without any file changing on your side. Since the same tool reads and writes a spreadsheet through a service account, that is the line to look at first when deciding how much you trust a setup, and the versioned tag syntax is already there if you would rather pin one yourself.

The credential is a key file on disk, and the folder id scopes it

Authentication is two environment variables on every platform, and the recommended path is a service account. On a Unix shell it is a path to the service account key file and a Drive folder identifier:

bash
# Replace with YOUR actual path and folder ID from the Google Setup step
export SERVICE_ACCOUNT_PATH="/path/to/your/service-account-key.json"
export DRIVE_FOLDER_ID="YOUR_DRIVE_FOLDER_ID"

The page gives the equivalent form for a Windows command shell and for PowerShell, and points at a longer section for the other options, which are OAuth and a credentials configuration variable. So there are three authentication routes and one recommendation. What the setup does not do is discuss the key file's lifetime or rotation; it is a long lived private key for an account that owns a folder in your Drive, and it is read by a process that, per the previous section, fetches its own code at startup. The folder identifier is doing real work here, because it is the boundary a tool call is meant to stay inside, so it is worth checking that the key's access actually matches that folder rather than assuming it.

Thirteen thousand tokens of tools before the conversation starts

The tool filtering section opens with the clearest problem statement in the repository. By default the server exposes all nineteen tools, which costs roughly 13,000 tokens before any conversation begins, and if you only need a few that is wasted context window. The fix is two mechanisms: a command line flag that takes a comma separated list, and an environment variable that takes the same list, with the page specifying comma separated and no spaces. A four tool subset is offered as the recommended starting point, a reader, a writer, a spreadsheet finder, and a tab navigator. The example client configuration shows both routes side by side, and the fallback behaviour is stated plainly: with neither the flag nor the variable set, everything is enabled. Nineteen names is not a large surface, but at roughly 680 tokens a tool the default configuration is a real tax on every request you send, and the fix is one environment variable.

The default set can share a spreadsheet, and there is no delete tool

Reading the nineteen names tells you what the agent is allowed to do, and the list is more revealing than the feature summary. There is create, update, batch update, rename and copy operations for sheets, a cell writer, several readers including formulas and a find operation, folder and spreadsheet listing, search, and a sharing tool that changes who can reach a spreadsheet. There is no delete tool and no clear cells tool anywhere in the list, which is an unusual shape for a write capable server and cuts both ways: you cannot ask it to destroy a sheet, but a batch update can still overwrite ranges wholesale. The two batch tools sit next to each other with almost identical names, and two of the readers differ only by whether they target one sheet or several. Nothing in the page describes a confirmation step for the sharing tool or a dry run mode, so the practical control is not a prompt but the filtering mechanism: enable only the four recommended tools and nothing else is reachable.

The image pipes an installer into itself and installs curl twice

The container file is short and worth reading for what it implies. It starts from the latest Alpine base, installs a shell, wget's companion, an init process, core utilities, and git, and then downloads the uv installer by piping a remote script straight into the shell inside the image. Two details stand out. The package list names curl on two separate lines of the same install command, which is harmless and suggests the list was assembled by appending. And the final command line runs the server through the environment runner rather than through the console script the package declares, so the container resolves the environment again at start instead of calling the entry point that the project metadata defines. On the positive side the interpreter version is copied in from a version file before the environment is created, so the image pins its Python deliberately, and the three stage layout builds a wheel in the middle stage and installs only that.

Four dependencies, and a version number that comes from a git tag

The project metadata is small in a way most server packages are not. There are four runtime dependencies: the protocol library, two Google authentication libraries, and the generated API client. The Python floor is 3.10. Everything else about the packaging is about the version, and the version is not written anywhere. It is declared dynamic, sourced from a plugin that reads it out of the repository, in strict mode, with a fallback of zero point zero point zero. That combination has two consequences worth knowing. A build from an untagged checkout falls back to that placeholder, and a tagged build reports whatever the tag says, which is why the newest two releases, 0.6.3 and 0.6.2, sit forty minutes apart on the same day. There is also a console script declared for the package, which the container does not use.

The last commit is from May, and a status file sits at the root

The repository's history is short and the recent end of it is quiet. The two newest tagged releases were both published on 2026-05-14, about forty minutes apart, the one before that on 2026-03-15, and the most recent commit is dated the same day as the newer pair. Nothing in the page claims a cadence and nothing suggests one, so the practical effect is that the newest thing the documentation describes is also the newest thing published, roughly five months ago. The root inventory is a little unusual. Alongside the source, tests, the lock file, the container file, and the licence there is a status file for outstanding work committed at the top level rather than in a documentation directory, and a configuration directory belonging to a different coding assistant, both of which are development scaffolding sitting where a reader looks for the package. Neither affects the install.

Editorial conclusion

Use this if you want an agent writing to a spreadsheet folder you already scoped, and enable tool filtering before the first conversation so the context cost is a few hundred tokens rather than thirteen thousand. Two things to settle first. Decide whether you accept a service account key file as the credential, because that file is what every tool call runs as. And pin something: the documentation's own advice is to always append the newest version tag, so the code your client runs can change between launches without you editing anything, and the newest two tagged releases were published forty minutes apart.

Frequently asked questions

Is there an MCP for Google Sheets?

This repository is one: a Python MCP server that bridges any MCP compatible client to the Google Sheets and Drive APIs through a defined set of tools. It is launched in one line with the uv package runner and configured with two environment variables.

How do I authenticate mcp-google-sheets?

A service account is strongly recommended. You point an environment variable at the path to its key JSON file and set a Drive folder identifier, which is the boundary the tools are meant to stay inside. OAuth and a credentials configuration variable are the other documented routes.

How many tools does mcp-google-sheets expose?

Nineteen, which the page puts at roughly 13,000 tokens of context before any conversation begins. You can filter with an include-tools flag or an enabled-tools environment variable, comma separated with no spaces, and a four tool subset is recommended. With neither set, everything is enabled.

Does mcp-google-sheets have a delete tool?

No delete tool appears among the nineteen listed names. What is there includes create, update, two batch update tools, rename, copy, and a sharing tool that changes who can reach a spreadsheet, so writes are broad while deletion is simply absent.

How is the mcp-google-sheets version determined?

The project metadata declares the version dynamically, sourced from the repository itself in strict mode with a fallback of zero point zero point zero. The newest tagged releases are 0.6.3 and 0.6.2, published about forty minutes apart on 2026-05-14.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. xing5/mcp-google-sheets on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xing5-mcp-google-sheets.svg)](https://hysenlabs.com/projects/xing5-mcp-google-sheets)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xing5-mcp-google-sheets.svg)](https://hysenlabs.com/projects/xing5-mcp-google-sheets)

Was this useful?