claude-code - 💡(How to fix) Fix [BUG] Cowork Windows: Gmail connector MCP server not responding after successful OAuth — "Authorization with the MCP server failed" [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48130Fetched 2026-04-15 06:32:18
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

Error Message

The Gmail connector fails to connect after completing OAuth. The connector settings page shows an error banner: "Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_6ac219f2e627af8f" Error persists through all of the above. Google Drive connector (same Google account) is Connected and working fine.

Error Messages/Logs

Error banner in claude.ai/settings/connectors: 4. Return to connectors page — error banner appears: "Authorization with the MCP server failed" 5. Restart Cowork — error persists The support reference code from the error banner is: ofid_6ac219f2e627af8f

Code Example

Error banner in claude.ai/settings/connectors:
"Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_6ac219f2e627af8f"

All Gmail MCP tool calls return:
"The connector's server isn't responding."
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The Gmail connector fails to connect after completing OAuth. The connector settings page shows an error banner: "Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_6ac219f2e627af8f"

All Gmail MCP tool calls return: "The connector's server isn't responding."

Steps taken before failure:

  • Clicked Configure on Gmail connector → completed Google OAuth flow
  • Restarted Cowork
  • Disconnected and reconnected Gmail connector entirely
  • Restarted Cowork again

Error persists through all of the above. Google Drive connector (same Google account) is Connected and working fine.

What Should Happen?

After completing OAuth, the Gmail connector should show "Connected" and MCP tool calls should succeed.

Error Messages/Logs

Error banner in claude.ai/settings/connectors:
"Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_6ac219f2e627af8f"

All Gmail MCP tool calls return:
"The connector's server isn't responding."

Steps to Reproduce

  1. Open claude.ai/settings/connectors in Cowork on Windows
  2. Click Configure next to Gmail
  3. Complete Google OAuth flow (grant permissions)
  4. Return to connectors page — error banner appears: "Authorization with the MCP server failed"
  5. Restart Cowork — error persists
  6. Disconnect Gmail connector, reconnect, complete OAuth again
  7. Restart Cowork again
  8. Attempt any Gmail MCP tool call — returns "The connector's server isn't responding"

Note: Google Drive (same Google account) is connected and working correctly.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Latest (Cowork desktop app, updated 2026-04-14)

Platform

Other

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

This is in the Claude Cowork desktop app (Windows), not the Claude Code CLI. Platform and Terminal fields above don't map cleanly — Platform set to "Other."

The support reference code from the error banner is: ofid_6ac219f2e627af8f

Google Calendar connector has the same issue (also fails to connect). Google Drive on the same Google account works fine, suggesting the issue is specific to the Gmail/Calendar MCP server rather than OAuth generally.

extent analysis

TL;DR

The issue is likely related to the MCP server connection for Gmail and Google Calendar connectors, and verifying the connector settings and permissions may help resolve the issue.

Guidance

  • Check the MCP server status and ensure it is responding correctly, as the error message suggests a server-side issue.
  • Verify that the credentials and permissions for the Gmail and Google Calendar connectors are correct and match the working Google Drive connector settings.
  • Attempt to connect to the Gmail and Google Calendar connectors using a different Google account to isolate if the issue is account-specific.
  • Review the support reference code ofid_6ac219f2e627af8f for any additional information or clues about the issue.

Example

No code snippet is provided as the issue seems to be related to the connector configuration and server-side response.

Notes

The issue is reported as a regression, and the fact that Google Drive is working correctly with the same Google account suggests that the issue is specific to the Gmail and Google Calendar connectors. The support reference code may provide additional information to help resolve the issue.

Recommendation

Apply workaround: Since the issue is likely related to the MCP server connection, attempting to connect to the Gmail and Google Calendar connectors using a different approach or verifying the server status may help resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING