fix: correct google-workspace MCP server command in config example#14
Merged
fix: correct google-workspace MCP server command in config example#14
Conversation
The google-workspace-mcp package exposes the executable as google-workspace-worker, not google-workspace-mcp. Using plain `uvx google-workspace-mcp` fails because uvx looks for an executable matching the package name. The fix is `uvx --from google-workspace-mcp google-workspace-worker`, where --from specifies the package to install and the final argument is the actual executable name. https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
Same fix as config.example.toml: the package google-workspace-mcp exposes the executable as google-workspace-worker, so the generated config must use --from to separate package name from executable name. https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
- setup/index.html: add inline 3-step OAuth guide shown when the tool is enabled; add GOOGLE_REDIRECT_URI to envVars pre-filled with the correct default (http://localhost:8080); use envDefaults fallback in generateToml so the redirect URI is written even if untouched - config.example.toml: add step-by-step OAuth comments explaining which APIs to enable, consent screen setup, and credential creation https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
Root cause: the package google-workspace-mcp expects GOOGLE_WORKSPACE_CLIENT_ID/SECRET/REFRESH_TOKEN/ENABLED_CAPABILITIES, not the GOOGLE_CLIENT_ID/SECRET/REDIRECT_URI names we had. - setup/index.html: replace all four env vars with correct names; add GOOGLE_WORKSPACE_ENABLED_CAPABILITIES with pre-filled default (all six services); update setup guide to use OAuth Playground flow for obtaining the refresh token - config.example.toml: same env var corrections + full 4-step OAuth Playground instructions including required scopes per capability https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
Root cause of 403 insufficientPermissions: the package defines no SCOPES constant — active scopes come entirely from the refresh token. If the token was minted without gmail.modify (or any other scope), every call to that API returns 403. The wizard guide said "add all Drive/Gmail/... scopes" which is too vague — users need the exact URL strings to paste into OAuth Playground. Now lists all 6 scope URLs explicitly with a warning that ALL must be selected together (missing any one causes 403). https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
Replaces the inline wall-of-text setup guide with a clean 4-step modal popup triggered by an "OAuth Setup Guide" button. The modal includes: - Numbered steps with clear titles and descriptions - Direct links to Google Cloud Console APIs library and OAuth Playground - Color-coded scope list (green monospace) showing all 6 required scopes - Warning box explaining that missing any scope causes 403 errors - Keyboard (Escape) and backdrop-click dismissal - Dark-theme styling consistent with the rest of the setup wizard https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq
Owner
Author
|
@claude please help for review |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The google-workspace-mcp package exposes the executable as
google-workspace-worker, not google-workspace-mcp. Using plain
uvx google-workspace-mcpfails because uvx looks for an executablematching the package name.
The fix is
uvx --from google-workspace-mcp google-workspace-worker,where --from specifies the package to install and the final argument
is the actual executable name.
https://claude.ai/code/session_01PxzWZ541PqYCSUfFNeJdfq