Google Sheets MCP

What henilcalagiya/google-sheets-mcp does

The henilcalagiya/google-sheets-mcp MCP server connects MCP-compatible clients to Google Sheets. It provides 25 tools for spreadsheet automation and supports CRUD operations across Google Sheets and tables. The documented operations include creating, reading, updating, and deleting sheets and related spreadsheet resources.

The server is intended for workflows where an AI assistant needs to work with Google Sheets rather than only describe or generate spreadsheet content. It can be used with clients including Claude Desktop, Continue.dev, Perplexity, and other MCP-compatible applications.

How it works

The henilcalagiya/google-sheets-mcp MCP server runs as a local MCP process through uvx. An MCP client starts the package and passes Google service-account configuration through its environment settings. The server then uses the Google Sheets API and Google Drive API to access the spreadsheets available to that account.

Before using the server, create a Google Cloud project, enable both required APIs, and create a service account with a JSON key. The target spreadsheet must be shared with the service account email and given Editor access. Without that share permission, the service account will not have access to the spreadsheet.

The configuration uses values from the service-account JSON file, including the project ID, private key ID, private key, client email, client ID, and client certificate URL. Existing configurations can use the older GOOGLE_-prefixed variable names as an alternative.

Setup and configuration

The project requires Python 3.10 or newer and the uv package manager, which provides the uvx command. The MCP client configuration runs:

{
  "command": "uvx",
  "args": ["google-sheets-mcp@latest"]
}

Add the service-account values to the client’s environment configuration. The README shows the following unprefixed names: project_id, private_key_id, private_key, client_email, client_id, and client_x509_cert_url. The private key must retain its multiline PEM formatting.

Google Cloud setup involves creating a project, enabling Google Sheets API and Google Drive API, creating a service account, and downloading a JSON key. Share each spreadsheet that the agent should manage with the service account email. The project is licensed under MIT.

Tools and capabilities

The henilcalagiya/google-sheets-mcp MCP server provides tools covering spreadsheet and table CRUD workflows. Based on the supplied documentation, these capabilities include:

• Creating Google Sheets resources
• Reading spreadsheet or table data
• Updating sheets and tables
• Deleting sheets or other supported resources
• Automating Google Sheets through MCP-compatible clients

The available tools are designed for general Google Sheets automation rather than a single fixed spreadsheet workflow. The supplied material does not provide individual tool names or detailed parameter schemas, so those details should be checked in the project source or the client’s tool listing.

Limitations and notes

Access depends on Google Cloud configuration and service-account permissions. The Google Sheets API and Google Drive API must both be enabled, and the spreadsheet must be explicitly shared with the service account. The README does not document OAuth user login; its stated authentication method is a Google service account.

The setup examples contain credential material such as private keys. Store those values in the MCP client’s protected environment configuration and avoid exposing them in source control or chat transcripts. The documentation confirms compatibility with Claude Desktop, Continue.dev, Perplexity, and other MCP clients, but does not provide client-specific setup instructions beyond the generic MCP configuration.

Getting started with this henilcalagiya/google-sheets-mcp MCP server

Always refer to the official documentation for the most accurate and up-to-date information.