Reported issues for Google Workspace MCP Server
Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to Google Workspace MCP Server.
Most discussed
Link to our build seperate full mcp
This scoped mcp is designed for my current work
We should link to options for folks who want ALL of the tools (or provide different scopes for analytics such as the GSC/GA options)
Seems like a clear product suite
Read the thread · 2026-08-07 · closed · 2 comments
Two workflow-comment fixes blocked on a token scope, and the scope picker still unverified
Tail end of conorbronsdon/personal-context#147, which is now closed. Seven of its nine items merged as #26–#29. These two need a person, so they're recorded here rather than left in a closed tracker.
1. Two workflow-file comment corrections — blocked on a token scope
Both fixes are written and rebased onto current main, but they cannot be pushed: the local gh token carries gist, read:org, repo and not workflow, so GitHub rejects any push touching .github/workflows/.
To ship:
Read the thread · 2026-08-02 · closed · 2 comments
Gate the tools/list payload figure with a computed test, or keep it hedged
Follow-up to #43. The README's context-cost figure has now gone stale twice in two consecutive PRs, so the general case is established rather than hypothetical.
- #34 replaced a hedge ("roughly 27 KB") with an exact
29,550 B— already wrong at merge time, because a review suggestion had lengthenedslides_batchUpdate's description after the measurement was taken. - #35 then added
attendeesandsendUpdateswith long descriptions, moving it a further ~950 B. - Measured on
d734eb5: **44 t
Read the thread · 2026-08-08 · closed · 1 comment
Repo description says 41 tools; the server reports 39
The GitHub repo description reads:
Curated MCP server for Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, and Tasks via the official gws CLI. 41 focused tools instead of 400.
The number is 39, confirmed three separate ways today:
- The server's own startup banner:
[gws-mcp] Starting with 39 tools from services: drive, sheets, calendar, docs, gmail, tasks - A live
tools/listagainst the container returns 39 entries. task createindocker/mcp-registryreported `39 tools f
Read the thread · 2026-08-03 · closed · 1 comment
drive_files_download fails on macOS: tmpdir() path rejected by gws CLI path validation
Problem
drive_files_download fails on macOS with:
Error downloading file: error[validation]: --output '/var/folders/rm/.../T/gws-dl-...' resolves to '/private/var/folders/rm/.../T/gws-dl-...' which is outside the current directory
Root Cause
Line 173 of build/index.js creates a temp file using an absolute path:
const tmpFile = join(tmpdir(), `gws-dl-${randomBytes(8).toString("hex")}`);
The gws CLI enforces that --output paths must resolve within the
Read the thread · 2026-04-09 · closed · external user · 1 comment
Publish workflow fails on any package.json change that isn't a version bump
publish.yml triggers on pushes to main filtered to paths: [package.json]. When that file changes for any reason other than a version bump, the job correctly skips the npm publish — and then fails anyway at the MCP-registry step.
Fired again today on 5ef26c9 (#34, which touched package.json only to add a google-slides keyword). Run 31251040096:
4 Check if package.json version is already published => succes
[Read the thread](https://github.com/conorbronsdon/gws-mcp-server/issues/44) · 2026-08-08 · closed · 0 comments
### Should *_batchUpdate tools advertise destructiveHint: true?
Surfaced by the #34 review. `docs_batchUpdate` and `sheets_batchUpdate` (and `slides_batchUpdate` once #34 lands) are classified `destructiveHint: false`, yet each API's Request union includes permanent delete operations (`deleteContentRange`, `deleteTab`, `deleteObject`, `deleteSlide`, etc. — verified against `gws schema` for docs and the live Slides API reference). The repo's own `ToolDef` contract defines destructive as 'irreversibly removes or overwrites user data (deletes)'.
Argument for k
[Read the thread](https://github.com/conorbronsdon/gws-mcp-server/issues/40) · 2026-08-07 · closed · 0 comments
### Windows: --json/--params values containing double quotes are corrupted into invalid JSON
Pre-existing on the win32 escaping path (`src/executor.ts` — `escapeJsonArg`/`escapeForCmd`): a body value containing a literal double quote comes out the other side as invalid JSON. Probed with a fake `gws` binary dumping `process.argv`:
summary: 'Bob & Alice "BB" sync' child --json raw -> {"summary":"Bob & Alice \BB\ sync"} // Bad escaped character — not valid JSON
Metacharacters themselves are safe — `& | > < ^ % ( ) !` all arrive literal with no execution (verified with injection
[Read the thread](https://github.com/conorbronsdon/gws-mcp-server/issues/37) · 2026-08-07 · closed · 0 comments
## Most recent
### Add readOnlyHint/destructiveHint annotations to tool definitions
Tools are currently registered without MCP [tool annotations](https://modelcontextprotocol.io/docs/concepts/tools#tool-annotations). Adding `annotations` would let clients reason about side effects and surface clearer consent UI:
- **`readOnlyHint: true`** for the read tools: `drive_files_list`, `drive_files_get`, `drive_files_export`, `drive_files_download`, `sheets_get`, `sheets_values_get`, `calendar_events_list`, `calendar_events_get`, `docs_get`, all `gmail_*_list`/`*_get` tools.
- **`dest
[Read the thread](https://github.com/conorbronsdon/gws-mcp-server/issues/5) · 2026-06-10 · closed · 0 comments
The remaining reports are on [the project's issue tracker](https://github.com/conorbronsdon/gws-mcp-server/issues).