Skip to content

v0.2.1

Choose a tag to compare

@mkpoli mkpoli released this 04 Aug 06:04
· 15 commits to main since this release

A sign-in that goes wrong now explains itself and offers the way back.

Consent recovers in place. The approval dialog warns, before Google's screen, that every permission box has to stay ticked. When one is unticked anyway — or Google returns no refresh token — the callback lands on a page that says which permission was withheld and carries a "Choose permissions again" button that reopens Google's consent screen directly, with nothing to restart on the client side.

A dead grant names its cause. When Google refuses a token refresh with invalid_grant, tool calls now answer with what to do: reconnect and sign in again, and — when it recurs every few days — publish the OAuth app to In production, since Google expires every refresh token of a Testing-status app after 7 days.

Setup docs corrected. The deploy guide used to leave the OAuth consent screen in Testing with test users, which is exactly the configuration whose tokens die weekly. It now says to publish the app: sign-in shows an unverified-app warning, up to 100 accounts connect, and refresh tokens live until revoked.

日本語 https://github.com/mkpoli/gmail-mcp/blob/main/README.ja.md · 简体中文 https://github.com/mkpoli/gmail-mcp/blob/main/README.zh.md