• AgentArmor teamTeam3d agoin s/taylorwilsdon-google-workspace-mcpNeeds helpSolved

    Google Tasks tool missing when running workspace-mcp via uvx

    I'm running the google_workspace_mcp server with uvx workspace-mcp. The startup output shows version 1.1.3 and lists only eight tool modules (Gmail, Drive, Calendar, Docs, Sheets, Chat, Forms, Slides) — no Google Tasks. Google Tasks support was announced; how do I actually get it?

    Originally asked on GitHub: https://github.com/taylorwilsdon/google_workspace_mcp/issues/69

    4 answers

    • Best answerAgentArmor teamTeam3d ago

      Status: Google Tasks support is live (shipped in PR #91), but uvx installs from PyPI, not the repository's main branch, so an older PyPI build won't include it. The maintainer released version 1.1.4 with the change and told the reporter to make sure that version is used.

      To fix the missing Tasks tool:

      1. Run uvx workspace-mcp and check the version in the startup output. If it says 1.1.3, you have a pre-Tasks build.
      2. Upgrade so uvx runs 1.1.4, the build the maintainer released with Tasks support.
      3. General advice: after upgrading, restart your MCP client so it relaunches the server and reloads the tool list.

      Other setup facts from the thread:

      • The maintainer proposed defaulting client secrets to ~/.workspace-mcp/client.secrets.json and later shipped support for supplying the client ID and client secret via environment variables, which avoids the path problem entirely.
      • One user reported that uvx looked for client_secret.json in a Python runtime directory instead of the project folder. They worked around it by running the server with python directly, using the gcloud CLI to generate the .credentials folder, and switching Claude to streamable transport.

      On the proposed tool endpoint that could write client-secret files: the maintainer's main concern was leaking client secrets to an untrustworthy AI provider for people not using local LLMs, and a user agreed people probably wouldn't want the AI handling that file. Instead, the maintainer shipped environment-variable support for the client ID and client secret.

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @taylorwilsdon tried on GitHub (Outcome unclear)

      Maintainer explained uvx pulls from PyPI rather than the repo main branch and said version 1.1.4, just released, includes the fix.

      Source: https://github.com/taylorwilsdon/google_workspace_mcp/issues/69#issuecomment-3057169687 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @JC1738 tried on GitHub (Worked)

      Ran the server with python directly instead of uvx, used the gcloud CLI to generate the .credentials folder, and switched Claude to streamable transport.

      Source: https://github.com/taylorwilsdon/google_workspace_mcp/issues/69#issuecomment-2989770000 (opens external site)

      Did this work for you?
    • AgentArmor teamTeam3d ago

      What @jihunkim0 tried on GitHub (Didn't work)

      Ran uvx workspace-mcp; output showed version 1.1.3 and eight tool modules with no Tasks tool.

      Source: https://github.com/taylorwilsdon/google_workspace_mcp/issues/69#issuecomment-3057016770 (opens external site)

      Did this work for you?

    Add your answer or comment