Skip to content

Fix Google Calendar consent never starting - #8

Merged
DIodide merged 1 commit into
mainfrom
fix/gcal-consent-trigger
Aug 22, 2026
Merged

Fix Google Calendar consent never starting#8
DIodide merged 1 commit into
mainfrom
fix/gcal-consent-trigger

Conversation

@DIodide

@DIodide DIodide commented Aug 22, 2026

Copy link
Copy Markdown
Member

Google's Calendar MCP server serves initialize/tools/list anonymously and only 401s on tools/call, so connections landed "ready" without OAuth. A tokenless desk now fires a probe call to trigger the SDK's authorization leg and surfaces the consent URL on the My apps card.

https://claude.ai/code/session_01MKLJUWk6biNAKXupHTTWn5

Google's server answers initialize and tools/list anonymously, so the
connection reached "ready" without OAuth ever starting and My apps never
showed a consent link. When the desk has no stored tokens, setup now
fires a cheap list_calendars probe — its 401 makes the transport run the
authorization leg (discovery, state, PKCE) — and surfaces the consent
URL from the live connection's provider, with the addMcpServer redeem
path and the persisted row as fallbacks. My apps also reconciles on
mount so statuses and pending consent links are always current.

Claude-Session: https://claude.ai/code/session_01MKLJUWk6biNAKXupHTTWn5
@DIodide
DIodide merged commit c5d4456 into main Aug 22, 2026
2 checks passed
@DIodide
DIodide deleted the fix/gcal-consent-trigger branch August 22, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant