Google Workspace MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_API_KEY | No | Google API key for public Google Sheets access. | |
| GOOGLE_OAUTH_TOKEN_FILE | No | Path to the stored Google OAuth refreshable token JSON file. | |
| GOOGLE_OAUTH_ACCESS_TOKEN | No | An existing Google OAuth bearer access token. | |
| GOOGLE_SERVICE_ACCOUNT_FILE | No | Path to the Google Cloud service account key JSON file. | |
| GOOGLE_OAUTH_CLIENT_SECRETS_FILE | No | Path to the Google OAuth client secret JSON file for desktop application authentication. |
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 |
|---|---|
| diagnose_google_authB | Return a quick summary of the active Google authentication setup. |
| resolve_google_fileB | Resolve basic metadata for a Google Docs, Sheets, or Drive file. |
| read_sheet_valuesC | Read raw Google Sheets values for an A1 range. |
| read_sheet_gridC | Read Google Sheets grid data including formatted values, formulas, notes, and links. |
| get_sheet_rowC | Fetch one Google Sheets row and map it to the header row. |
| search_sheetC | Search text across one sheet or all sheets and return matching cells. |
| sheet_to_jsonB | Convert a Google Sheets tab into JSON records using the header row. |
| inspect_sheet_imagesB | Inspect Google Sheets images via XLSX export and detect IMAGE() formulas. |
| read_google_docB | Read a Google Doc as structured JSON with text, tables, and image metadata. |
| download_google_doc_imagesC | Download image objects from a Google Doc to a local folder. |
| export_google_fileB | Export a Google Workspace file to PDF, XLSX, HTML zip, Markdown, or plain text. |
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 11 tools
Most tools have distinct purposes targeting specific Google Workspace components like Docs or Sheets, but some overlap exists between read_sheet_grid and read_sheet_values which both read sheet data with slightly different scopes. The descriptions help clarify the differences, but an agent might occasionally confuse these similar tools.
Tool names follow a consistent verb_noun pattern throughout, such as diagnose_google_auth and export_google_file, with clear and descriptive naming. There are minor deviations like sheet_to_json which uses 'to' instead of a verb, but overall the naming is highly predictable and readable.
With 11 tools, the count is well-scoped for a Google Workspace server, covering authentication, file operations, and detailed sheet/document interactions. Each tool earns its place by addressing specific needs without being excessive or insufficient for the domain.
The tool set covers reading and exporting files well, but there are notable gaps in CRUD operations for the domain, such as creating, updating, or deleting Google Docs or Sheets. While tools like export_google_file and read_google_doc handle retrieval, the lack of write or modify tools limits full lifecycle coverage.