gsheetmcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host to bind to in SSE mode | 0.0.0.0 |
| MCP_PORT | No | Port to listen on in SSE mode | 8000 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' or 'sse' | stdio |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_sheet_dataD | – |
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 1 tool
With only one tool, there is no ambiguity. The single tool is distinctly the only option.
The single tool uses clear snake_case naming, consistent with itself.
A single tool for a Google Sheets integration is far too few; typical operations require multiple tools (e.g., create, update, delete).
The server is severely incomplete, offering only a read operation (get_sheet_data) with no ability to modify or manage sheets.