A Google OAuth connection can fail after a week when its app is External and still in Testing. Refresh tokens expire after seven days in this setup, except when only basic identity scopes are requested. GA4 and Search Console access go beyond that exception. 1
Check the OAuth app behind the connection
Open the Google Cloud project that owns the OAuth client used by your MCP server. Check its audience and publishing status. The seven-day rule has an exception when the app requests only basic identity scopes such as openid, email and profile; GA4 or Search Console data access goes beyond that exception. 1
A one-hour access-token lifetime is a separate issue. Short-lived access tokens are expected; the refresh token lets the client obtain replacements. Inspect the returned expires_in value instead of assuming the two tokens expire together. 25
Choose the appropriate app status
For a development test, signing in again may be sufficient. For ongoing use, review whether the app is ready to move to Production. Publishing and verification are separate states: publishing alone does not make an app Google-verified. 3
Check the requested scopes, audience and verification requirements first. Personal-use apps can qualify for an exception; public apps using sensitive or restricted scopes have additional requirements. After the appropriate configuration change, reconnect through the tool’s normal authorization flow. 45
If the error is invalid_grant
Do not treat that message as proof of the seven-day rule. It can also indicate an invalidated token or another authorization problem. Check when the failure occurs, confirm the OAuth client and inspect the error details. If the failure happens immediately, investigate those details before changing the app’s publishing status. 5