Broken OAuth redirect URI for google drive MCP server

[bobbravo2]

Summary

Google Drive MCP shows as connected (green) in Integrations, but agent still attempts OAuth re-auth with a broken redirect URI (Error 400: redirect_uri_mismatch).

What Happened

User was trying to have an agent search their Google Drive. The Integrations tab showed Google Drive MCP as green/connected. The agent called get_drive_file_content, received an authentication error, then generated an OAuth authorization URL and presented it as a clickable link.

When the user clicked the link (trusting the agent and the "green" status indicator), Google rejected it with:

Access blocked: This app's request is invalid
Error 400: redirect_uri_mismatch

The link was a dead end — the OAuth flow could never succeed due to the mismatched redirect URI.

Impact

• User trusted the green integration status and followed agent instructions
• The OAuth link presented by the agent is non-functional
• No recovery path was offered to the user
• Misleading UX: integration shows connected but fails at runtime

Screenshots

Environment

vteam-uat, session id 8c23f023-c0c5-4a58-be71-20d14ac72cca
Tested via the hosted UI.
Showing release verions 0.2.5 in the UI.