claude-code - 💡(How to fix) Fix Gmail MCP connector blocked by Google for gmail.modify scope [1 comments, 2 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#51790Fetched 2026-04-22 07:52:46
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×3closed ×1commented ×1unlabeled ×1

Error Message

the connector attempts label operations (add or remove labels), it returns a 403 Permission Denied error.

Error Messages/Logs

  1. Run the agent — the label operation returns a 403 Permission Denied error
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 MCP connector available at claude.ai/settings/connectors only appears to be authorized for read access. When the connector attempts label operations (add or remove labels), it returns a 403 Permission Denied error.

When attempting to re-authorize the connector to grant broader permissions, Google displays a hard block: "This app is blocked. This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access." There is no "Advanced" option to proceed.

Impact: Any scheduled agent that uses the Gmail connector cannot modify labels, making it impossible to track which emails have been processed. This causes duplicate processing on subsequent runs.

Environment: Claude Code scheduled agent (remote trigger), Gmail MCP connector (gmailmcp.googleapis.com)

What Should Happen?

Expected behavior: The Claude.ai Gmail connector should be verified by Google for gmail.modify scope so that scheduled agents can read, label, and organize Gmail messages.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

  1. Go to claude.ai/settings/connectors and connect the Gmail integration
  2. Create a scheduled remote agent that uses the Gmail connector
  3. In the agent prompt, instruct it to add or remove a label using the label_message or unlabel_message tools
  4. Run the agent — the label operation returns a 403 Permission Denied error
  5. Attempt to re-authorize the Gmail connector with broader permissions — Google displays a hard block: "This app is blocked" with no option to proceed

Expected: Label operations succeed Actual: 403 on label operations; re-authorization blocked by Google

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

No response

Claude Code Version

2.1.117

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

No response

extent analysis

TL;DR

The Gmail MCP connector needs to be verified by Google for the gmail.modify scope to enable label operations.

Guidance

  • The issue is likely due to the connector only having read access, which is insufficient for label operations.
  • To verify the current scope of the Gmail connector, check the authorization settings in the Google Cloud Console.
  • Attempt to re-authorize the connector with the gmail.modify scope to grant broader permissions.
  • If Google blocks the re-authorization, consider reaching out to Google support to resolve the issue.

Example

No code snippet is provided as the issue is related to authorization and scope configuration.

Notes

The issue may be specific to the Claude Code version (2.1.117) or the Anthropic API platform, and resolving the issue may require coordination with Google support.

Recommendation

Apply a workaround by attempting to re-authorize the connector with the gmail.modify scope, and if that fails, reach out to Google support for assistance.

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

claude-code - 💡(How to fix) Fix Gmail MCP connector blocked by Google for gmail.modify scope [1 comments, 2 participants]