Google Sheets MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level for the server | INFO |
| SERVER_NAME | No | Server configuration name | google-sheets-mcp-server |
| SHEET_API_KEY | No | Your Google API key for accessing public spreadsheets (optional fallback to OAuth) | |
| SERVER_VERSION | No | Server version | 1.0.0 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_sheet_dataC | Read data from a Google Sheet by spreadsheet ID and range |
| get_sheet_metadataC | Get metadata about a Google Spreadsheet |
| list_sheetsC | List all sheets/tabs in a Google Spreadsheet |
| search_sheet_dataC | Search for specific data in a Google Sheet |
| get_range_dataC | Get data from a specific range with formatting options |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Google Sheets Reader | Access and read Google Sheets data |
TDQS
Scored across 5 tools
There is significant overlap between get_range_data and read_sheet_data, as both retrieve data from a sheet range, potentially causing confusion. However, get_range_data mentions formatting options while read_sheet_data specifies spreadsheet ID, providing some differentiation. The other tools have clearer distinct purposes (metadata, listing, searching).
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_range_data, list_sheets, search_sheet_data). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 5 tools, the count is reasonable for a Google Sheets server, covering core operations like reading, listing, and searching. It is slightly thin for a full-featured Sheets API but adequate for basic interactions, lacking tools for writing or updating data.
The tool set is severely incomplete for a Google Sheets domain, as it only supports read operations (get, list, search) with no create, update, or delete capabilities. This creates significant gaps that will hinder agents from performing common workflows like editing or managing sheets.