google-sheets-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JWT_SECRET | Yes | A long random string used to sign and verify JWT tokens, at least 32 characters, generated via crypto.randomBytes(32).toString('hex') | |
| SPREADSHEET_ID | Yes | The ID of the Google Sheet from its URL | |
| GOOGLE_CLIENT_ID | Yes | Google OAuth client ID from Google Cloud Console | |
| GOOGLE_REDIRECT_URI | Yes | OAuth redirect URI, must match Google Cloud Console and Vercel deployment URL, e.g., https://YOUR-VERCEL-APP.vercel.app/oauth/google/callback | |
| GOOGLE_CLIENT_SECRET | Yes | Google OAuth client secret from Google Cloud Console |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| append_rowB | Append a row to a Google Sheet |
| read_sheetC | Read data from a Google Sheet |
| update_cellB | Update a specific cell in a Google Sheet |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct operation: appending a row, reading a sheet, and updating a cell. There is no overlap in functionality, making it clear to an agent which tool to select.
All tool names follow the consistent verb_noun pattern: append_row, read_sheet, update_cell. This makes the set predictable and easy to understand.
With 3 tools, the set is slightly lean but still reasonable for basic Google Sheets operations. It covers create (append), read, and update, but lacks a delete operation, which is a minor shortfall.
The set covers core CRUD operations except delete, and lacks ability to create or delete sheets themselves. Agents may need additional functionality for full lifecycle management, indicating notable gaps.