Scheduled triggers: MCP connectors fail to load in remote sessions

Problem

MCP connectors configured on a scheduled trigger's mcp_connections field are not loaded in the remote session. The agent reports tools as unavailable despite the connectors being properly configured in the user's account and specified in the trigger config.

Setup

Connectors configured (all showing as connected/configured in claude.ai/settings):

• Linear (mcp.linear.app/mcp)
• Slack (mcp.slack.com/mcp)

Trigger config includes mcp_connections with correct connector UUIDs and URLs:

"mcp_connections": [
  {"connector_uuid": "38f1d967-...", "name": "Linear", "url": "https://mcp.linear.app/mcp"},
  {"connector_uuid": "806a7f77-...", "name": "Slack", "url": "https://mcp.slack.com/mcp"}
]

The update API returns 200 OK and the GET confirms the connections are stored.

Observed behavior

When the trigger runs, the remote agent reports:

• "Linear MCP tools unavailable in this environment"
• "Slack MCP tools unavailable in this environment"

This happens consistently across:

• Default environment (env_01AwxuhsJSy6RpaTqnUY3Fim)
• Full environment (env_01CM4LBvPDii49zkDFbo4nDZ)
• Multiple runs over several hours
• After re-adding connectors in the Customize page

The gh CLI is also unavailable in both environments, despite GitHub Integration being connected.

Expected behavior

MCP tools from configured connectors should be available to the remote agent, same as they are in interactive claude.ai conversations.

Workaround

None currently. The agent's prompt includes graceful fallbacks (skip Linear/Slack steps if unavailable), but the core integrations don't work.

Additional context

• The same connectors work fine in interactive claude.ai conversations
• The trigger's allowed_tools field correctly specifies Bash, Read, Write, etc. and those work
• Git operations work correctly in the remote session
• Related issue: #44771 (permission prompts in remote sessions)