Complete Google OAuth verification for MCP server redirect domain (clickup-prod.com)
planned
Mostafa Shabanpour
When connecting any Google Workspace MCP server (official or custom) that uses OAuth, Google blocks the authentication flow with "Access blocked: clickup-prod.com has not completed the Google verification process" (Error 403: access_denied). This happens because ClickUp's MCP redirect URI (https://search.clickup-prod.com/connect/mcp) belongs to an unverified OAuth application from Google's perspective. Even when users provide their own OAuth Client ID and Secret, the redirect still goes through clickup-prod.com, which triggers Google's block. This completely prevents connecting any Google service via OAuth to Super Agents, including Google's own official MCP servers for Drive, Gmail, and Calendar. Please complete Google's OAuth app verification for the clickup-prod.com domain so users can authenticate with their Google accounts through MCP connections. This is a critical blocker for any Google Workspace MCP integration.
Log In
Arkady Sokolov
updated the status to
planned
Arkady Sokolov
Thanks for reporting this! We're actively investigating the Google OAuth verification issue with the clickup-prod.com redirect domain. If you could also file a bug report directly at https://clickup.com/support, that'll help us accelerate resolution since it creates a tracked ticket on our end. Appreciate the detailed write-up.
Arkady Sokolov
Merged in a post:
Complete Google OAuth verification for MCP server redirect domain (clickup-prod.com)
Mostafa Shabanpour
When connecting any Google Workspace MCP server (official or custom) that uses OAuth, Google blocks the authentication flow with "Access blocked: clickup-prod.com has not completed the Google verification process" (Error 403: access_denied). This happens because ClickUp's MCP redirect URI (https://search.clickup-prod.com/connect/mcp) belongs to an unverified OAuth application from Google's perspective. Even when users provide their own OAuth Client ID and Secret, the redirect still goes through clickup-prod.com, which triggers Google's block. This completely prevents connecting any Google service via OAuth to Super Agents, including Google's own official MCP servers for Drive, Gmail, and Calendar. Please complete Google's OAuth app verification for the clickup-prod.com domain so users can authenticate with their Google accounts through MCP connections. This is a critical blocker for any Google Workspace MCP integration
Autopilot
Merged in a post:
Complete Google OAuth verification for MCP server redirect domain (clickup-prod.com)
Mostafa Shabanpour
When connecting any Google Workspace MCP server (official or custom) that uses OAuth, Google blocks the authentication flow with "Access blocked: clickup-prod.com has not completed the Google verification process" (Error 403: access_denied). This happens because ClickUp's MCP redirect URI (https://search.clickup-prod.com/connect/mcp) belongs to an unverified OAuth application from Google's perspective. Even when users provide their own OAuth Client ID and Secret, the redirect still goes through clickup-prod.com, which triggers Google's block. This completely prevents connecting any Google service via OAuth to Super Agents, including Google's own official MCP servers for Drive, Gmail, and Calendar. Please complete Google's OAuth app verification for the clickup-prod.com domain so users can authenticate with their Google accounts through MCP connections. This is a critical blocker for any Google Workspace MCP integration.