Google Sheets

io.github.mcp-zPublished by GitHub account mcp-zv2.4.2Updated Oct 24, 2026

Google Sheets integration with OAuth, spreadsheet management, batch operations, and formatting

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Lets an assistant work with Google Sheets through OAuth, including spreadsheet management, batch operations and formatting.

What you can do
This server connects an assistant to Google Sheets. According to its description it covers OAuth-based authentication, spreadsheet management, batch operations and formatting. Configuration options suggest it can run with OAuth client credentials or a service account key file, and can operate in different authentication and dynamic client registration modes. It runs as a local stdio process rather than a hosted endpoint.
When to use it
Use it when you want an assistant to read, create, update or format Google Sheets content, or to apply batch changes across a spreadsheet, from a desktop MCP client. It suits workflows where spreadsheet data is the working surface rather than a general database.
Requirements
Runs locally as a stdio process, typically via npx from the npm package @mcp-z/mcp-sheets, so Node.js is needed. Google authentication is configured through environment variables: GOOGLE_CLIENT_ID is required for OAuth modes, GOOGLE_CLIENT_SECRET is optional for public clients, and GOOGLE_SERVICE_ACCOUNT_KEY_FILE is required for service-account mode. Other settings include AUTH_MODE, BASE_URL, DCR_MODE, DCR_STORE_URI, DCR_VERIFY_URL, HEADLESS, LOG_LEVEL, PORT, REDIRECT_URI and RESOURCE_STORE_URI
Before you install
The server handles Google OAuth credentials: GOOGLE_CLIENT_SECRET is a secret, and GOOGLE_SERVICE_ACCOUNT_KEY_FILE points to a service account private key file, so protect both and avoid exposing them in logs or shared configs. Spreadsheet edits, batch operations and formatting can modify or overwrite existing data in your Google account, so review what the assistant is about to change. Depending on AUTH_MODE and DCR settings, OAuth and registration endpoints may be exposed over HTTP via BASE_UR

Installation

In SourceWeft

  1. Open Google Sheets in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v2.4.2LatestOct 12, 2026
  2. v2.4.1Oct 12, 2026
  3. v2.4.0Oct 10, 2026
  4. v2.3.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.