Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Gmail MCP connector not visible to scheduled remote agents (CCR) despite being connected in Customize [2 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#58901•Fetched 2026-05-14 03:36:33
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
milindgandhe-uxmilindgandhe-ux
Participants
github-actions[bot]github-actions[bot]milindgandhe-uxmilindgandhe-ux
Timeline (top)
labeled ×4commented ×2closed ×1

When a Gmail MCP connector is connected via claude.ai/customize/connectors, it does not appear in the connector list available to scheduled remote agents (routines/CCR). The /schedule skill consistently returns "No connected MCP connectors found" even after the connector is visibly connected in the UI.

The connector did get attached when the routine was created via the RemoteTrigger API directly, suggesting the connector exists but isn't being surfaced by the API endpoint the skill uses to enumerate available connectors.

Root Cause

When a Gmail MCP connector is connected via claude.ai/customize/connectors, it does not appear in the connector list available to scheduled remote agents (routines/CCR). The /schedule skill consistently returns "No connected MCP connectors found" even after the connector is visibly connected in the UI.

The connector did get attached when the routine was created via the RemoteTrigger API directly, suggesting the connector exists but isn't being surfaced by the API endpoint the skill uses to enumerate available connectors.

Fix Action

Workaround

Create the routine via the RemoteTrigger API directly — the connector attaches automatically.

RAW_BUFFERClick to expand / collapse

Summary

When a Gmail MCP connector is connected via claude.ai/customize/connectors, it does not appear in the connector list available to scheduled remote agents (routines/CCR). The /schedule skill consistently returns "No connected MCP connectors found" even after the connector is visibly connected in the UI.

The connector did get attached when the routine was created via the RemoteTrigger API directly, suggesting the connector exists but isn't being surfaced by the API endpoint the skill uses to enumerate available connectors.

Steps to reproduce

  1. Connect Gmail at claude.ai/customize/connectors
  2. Use the /schedule skill to create a routine
  3. Skill reports no connectors available

Expected behavior

Connected connectors should be listed and selectable when creating scheduled routines.

Workaround

Create the routine via the RemoteTrigger API directly — the connector attaches automatically.

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…

FAQ

Expected behavior

Connected connectors should be listed and selectable when creating scheduled routines.

#api#authentication issue#prompt issue#agent setup#task chaining

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 not visible to scheduled remote agents (CCR) despite being connected in Customize [2 comments, 2 participants]