{ "SchemaVersion": "1", "Kind": "DirectoryIssues", "Slug": "google-workspace", "Name": "Google Workspace", "CanonicalUrl": "https://askpod.ai/mcp/google-workspace/issues", "ServerUrl": "https://askpod.ai/mcp/google-workspace", "IssueTotal": 26, "Held": 20, "Issues": [ { "Title": "[BUG] manage_docs get only returns the first tab of a multi-tab Google Doc", "Excerpt": "`manage_docs` with operation `get` returns the content of the first tab only. There's no error and nothing in the response to indicate the document has other tabs, so the partial content reads like the whole file.\n\n**Steps To Reproduce**\n\n1. Create a Google Doc with several tabs and put different text in each one.\n2. Call `manage_docs` with `operation: get`, the document ID, and an authenticated account email.\n3. Compare what comes back against the document. Only the first tab is there.\n\n**Expec", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/152", "PublishedAt": "2026-07-27T10:12:13.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Expose slides.presentations.batchUpdate", "Excerpt": "**Method:** `slides.presentations.batchUpdate` (`POST`)\n\n**Google's description:** Applies one or more updates to the presentation. Each request is validated before being applied. If any request is not valid, then the entire request will fail and nothing will be applied. Some requests have replies to give you some information about how they are applied. Other requests do not need to return information; these each return an empty reply. The order of replies matches that of the requests. For examp", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/151", "PublishedAt": "2026-07-27T03:34:27.000Z", "State": "open", "Comments": 1, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Bug: Server fails to start on Windows due to hardcoded PATH delimiter (using : instead of ;)", "Excerpt": "Description: Hi! I love the concept of this MCP server, but I ran into a hard crash when trying to run it on a Windows machine.\n\nIt looks like the server assumes the PATH environment variable is separated by colons (:), which is true for macOS and Linux. However, on Windows, the PATH is separated by semicolons (;).\n\nBecause of this, when the server boots up and tries to locate the gws executable, it fails to parse the Windows path correctly and the server crashes immediately.\n\nTo Reproduce:\n\nTry", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/150", "PublishedAt": "2026-07-20T09:57:32.000Z", "State": "closed", "Comments": 1, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Server outlives its MCP client, then spins at 100% CPU — uncaughtException handler loops forever on a dead stderr", "Excerpt": "## Environment\n\n- `@aaronsb/google-workspace-mcp` 4.0.1, launched via `npx -y @aaronsb/google-workspace-mcp` (stdio transport)\n- Client: Claude Code 2.1.x on macOS (Darwin 25.5.0)\n- Node v24.8.0\n\n## Symptom\n\nAfter a Claude Code session ends uncleanly (crash, force-quit, killed terminal), the server process does not exit. Worse, it doesn't just idle — it pegs one CPU core at 100% indefinitely. Today I found two orphaned instances that had each burned 31 minutes of CPU time in 31 minutes of wall t", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/149", "PublishedAt": "2026-07-16T14:51:42.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Legacy streamable-http: credential refresh triggers session rebinding error for multi-account use", "Excerpt": "### Bug Description\n\nWhen using Google Workspace MCP in legacy streamable-http multi-user mode, stored credentials are successfully refreshed after a server restart, but the request fails because the MCP session attempts to rebind to a different Google identity.\n\nThe server then incorrectly starts a new OAuth flow even though valid refreshed credentials already exist.\n\nThis appears to affect environments where a single MCP server is used with multiple Google accounts by supplying user_google_ema", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/134", "PublishedAt": "2026-07-10T00:20:02.000Z", "State": "closed", "Comments": 2, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "reply silently ignores attachments/draft params — always sends live, attachment never attaches", "Excerpt": "## Summary\n\n`reply` silently ignores both the `attachments` and `draft` parameters — despite the tool's own JSON schema documenting `draft` as \"forced true when attachments present,\" implying this applies across operations. In practice, only `send` implements that behavior; `reply` sends live every time, with no attachment, no matter what's passed.\n\n## Root cause (exact location)\n\nIn `services/gmail/patch.js`, the `customHandlers.send` handler (lines 190–232) correctly implements both parameters", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/132", "PublishedAt": "2026-07-01T19:22:33.000Z", "State": "closed", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "[FEATURE] Generic api_call operation for arbitrary Workspace API endpoints", "Excerpt": "## Problem Statement\nOperations are limited to what's surfaced in the YAML manifest. Anything in the underlying `@googleworkspace/cli` / Google API surface that isn't in the manifest is unreachable without a manifest edit + release. For \"agent can do anything\" use cases, that long tail matters.\n\n## Proposed Solution\nA generic `api_call` operation: authenticated request to an arbitrary `*.googleapis.com` endpoint using the active account's credentials. Inputs: `method`, `path`/`url`, `query`, `bo", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/131", "PublishedAt": "2026-06-26T00:34:15.000Z", "State": "open", "Comments": 0, "Reporter": "External", "Rank": "recent", "Extractor": "github_issue" }, { "Title": "Proposal: opt-in read-only OAuth scopes (access: 'read')", "Excerpt": "## Proposal\n\nAdd an **opt-in** `access: 'read' | 'readwrite'` option to account authentication. When set to `'read'`, it requests the read-only variant of each service scope (`gmail.readonly`, `drive.readonly`, `calendar.readonly`, …) instead of the current read/write scopes (`gmail.modify`, `drive`, `calendar`, …).\n\n**The default stays `'readwrite'`** — fully backward-compatible. No behavior changes unless a user opts in.\n\n## Motivation\n\nIn multi-account setups it's common to want least privile", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/130", "PublishedAt": "2026-06-03T05:04:29.000Z", "State": "open", "Comments": 2, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "[FEATURE] manage_email send operation lacks from parameter for Send As aliases", "Excerpt": "## Problem Statement\nThe `manage_email` send operation has no `from` parameter. The sender is controlled entirely by the account credentials, so Gmail always falls back to the account's default Send As address. There is no way to specify a verified Send As alias as the sender through the MCP.\n\n## Proposed Solution\nAdd an optional `from` parameter to the `manage_email` send operation that accepts either a plain address (`user+alias@gmail.com`) or an RFC 2822 formatted string (`Agent Name ` to the `gws` CLI, but `gws calendar +insert` only accepts `--attendee ` (singular, can be repeated). The unknown plural flag is rejected at validation time.\n\n## Reproduction\n\n```json\n{\n \"operation\": \"create\",\n \"email\": \"user@example.com\",\n \"summary\": \"Test\",\n \"start\": \"2026-05-01T00:00:00+05:30\",\n \"end\": \"2026-05-01T01:00:00", "SourceUrl": "https://github.com/aaronsb/google-workspace-mcp/issues/116", "PublishedAt": "2026-04-30T16:28:21.000Z", "State": "closed", "Comments": 2, "Reporter": "External", "Rank": "top", "Extractor": "github_issue" }, { "Title": "manage_drive.listPermissions returns \"No files found\" for valid fileId", "Excerpt": "## Summary\n\n`manage_drive.listPermissions` returns the error text `No files found` even when the provided `fileId` refers to an existing, owned file. `get` on the same file returns proper metadata and other ops (`addComment`, `copy`, `download`, `delete`) work normally.\n\n## Version\n\n`@aaronsb/google-workspace-mcp@2.6.1` invoked via MCP stdio (direct `node build/index.js`, not through a gateway) on Linux, Node 20.\n\n## Repro\n\n1. Upload a file: `manage_drive` with `{\"operation\":\"upload\",\"email\":\"