[BUG] CCR scheduled triggers fail to load MCP connector tools in unattended runs
Resolved 💬 6 comments Opened Apr 1, 2026 by adityadnv-aviso Closed Apr 5, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Claude.ai connectors attached to a scheduled remote trigger load MCP tools
successfully during manual/test runs but fail with "No MCP tools are loaded
in this session" when the same trigger fires on a cron schedule unattended.
Environment
- Claude Code version: latest
- Platform: macOS
- Trigger type: Scheduled remote trigger (CCR)
- Connectors: Gmail, Google Calendar, Granola, Atlassian (Jira)
## Steps to Reproduce
- Connect MCP connectors at claude.ai/settings/connectors
- Create a scheduled trigger via RemoteTrigger API with those connectors
attached in mcp_connections
- Manually run the trigger (action: "run") — MCP tools load successfully
- Wait for the cron schedule to fire automatically (unattended)
- Check run logs — agent reports "No MCP tools are loaded in this session"
What Should Happen?
Expected Behavior
MCP connector tools (Gmail, Calendar, etc.) should load in both manual and
scheduled runs since the same connector UUIDs are used in both cases.
Error Messages/Logs
## Actual Behavior
Manual/test runs: MCP tools load correctly, agent can call Gmail, Calendar etc.
Scheduled (cron) runs: "No MCP tools are loaded in this session" — agent sees
only built-in tools (Bash, Read, Write, etc.)
## Hypothesis
The connector OAuth tokens appear to be scoped to interactive/browser sessions.
Manual runs piggyback an active user session for token exchange. Scheduled
unattended runs have no live session and need stored offline refresh tokens —
these either aren't being stored or weren't granted offline_access scope during
the connector setup flow.
## Additional Observation
After disconnecting and reconnecting connectors, the schedule skill API
consistently returns "No connected MCP connectors found" even though connectors
are visible and active in claude.ai/settings/connectors — suggesting a sync
lag between the UI and the CCR API layer.
## Trigger ID (for investigation)
trig_01KWr7GFhTDZCopuHZXZ6G8i
Steps to Reproduce
## Steps to Reproduce
- Connect MCP connectors at claude.ai/settings/connectors
- Create a scheduled trigger via RemoteTrigger API with those connectors
attached in mcp_connections
- Manually run the trigger (action: "run") — MCP tools load successfully
- Wait for the cron schedule to fire automatically (unattended)
- Check run logs — agent reports "No MCP tools are loaded in this session"
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.89
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗