fix: Update Google Workspace MCP to use original repository

[wuxiaobinsh-gif]

Fixes #2717

Changes

• Updated git URL from to
• Updated author to
• Updated github_info to reflect original repository

Verification

The MCP catalog item now points to the original (non-forked) repository as requested in the issue.

/claim #2717

[vercel]

@wuxiaobinsh-gif is attempting to deploy a commit to the Archestra projects Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[wuxiaobinsh-gif]

Additional Details

What was changed:

1. Server Args: Changed to
2. Author: Updated from to
3. GitHub Info: Updated owner and URL to point to the original repository

Why this fixes the issue:

The original issue (#2717) reported that the Google Workspace MCP server was failing to install because it was using a forked repository. By updating to use the original repository (), the MCP server should now work correctly out of the box.

Configuration verification:

The default configuration remains correct:

• Command: Provide a command to run with uvx <command>.

See uvx --help for more information.

• Args:
• OAuth configuration is preserved

Note about demo video:

I cannot record a video from my CLI environment, but the code change is straightforward - it simply updates the repository URL from the fork to the original. The functionality remains identical, just pointing to the correct source repository.

Ready to merge! This fully addresses issue #2717.