Scheduled remote triggers (CCR) can't access claude.ai MCP connectors — tools not available in automated runs

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?

When a scheduled remote trigger is configured with mcp_connections (using claude.ai OAuth connectors for Gmail and Slack), the MCP tools are not available
when the trigger runs automatically on its cron schedule.

What Should Happen?

MCP tools configured via mcp_connections in the trigger should be available to the remote agent during automated runs.

Error Messages/Logs

The agent outputs:
  ▎ "The Gmail and Slack tools are not available in this environment. These tools are MCP server tools that need to be configured in
  ~/.claude/settings.json"

Steps to Reproduce

Steps to reproduce

1. Create a scheduled remote trigger with mcp_connections referencing claude.ai OAuth connectors (e.g. Gmail connector UUID, Slack connector UUID)
2. Let it run on its cron schedule (or trigger via Run Now from the API)
3. The remote agent does not see the MCP tools and fails

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Sonnet 4.6 (model ID: claude-sonnet-4-6).

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

When a scheduled remote trigger is configured with mcp_connections (using claude.ai OAuth connectors for Gmail and Slack), the MCP tools are not available
when the trigger runs automatically on its cron schedule.

The agent outputs:
▎ "The Gmail and Slack tools are not available in this environment. These tools are MCP server tools that need to be configured in
~/.claude/settings.json"

Steps to reproduce

1. Create a scheduled remote trigger with mcp_connections referencing claude.ai OAuth connectors (e.g. Gmail connector UUID, Slack connector UUID)
2. Let it run on its cron schedule (or trigger via Run Now from the API)
3. The remote agent does not see the MCP tools and fails

Expected behavior
MCP tools configured via mcp_connections in the trigger should be available to the remote agent during automated runs.

Actual behavior
Tools are not available. The agent looks for local settings.json config instead of using the cloud connectors passed via mcp_connections.

Workaround
Opening the trigger manually in claude.ai and running it from the browser context works — MCP tools are available in that context.

Environment

• Claude Code scheduled remote triggers (CCR)
• MCP connectors: claude.ai Gmail, claude.ai Slack (OAuth-based cloud connectors)