[BUG] Remote triggers fail to load OAuth MCP connectors in execution environment

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?

Remote triggers with OAuth MCP connectors (Slack, Atlassian) stopped working on 1 April 2026.
Every scheduled and manual run fails — the MCP tools are reported as unavailable in the execution environment. The same connectors work correctly in a local Claude Code session, confirming the tokens are valid and the issue is specific to the remote trigger environment.

What Should Happen?

The remote trigger execution environment should load the OAuth credentials for configured MCP connectors and make those tools available, the same way they work in a local session.

Error Messages/Logs

"The required Slack and Jira MCP tools are not available in this environment."

Steps to Reproduce

Steps to reproduce

1. Configure a remote trigger with one or more OAuth MCP connectors (e.g. Slack via mcp.slack.com/mcp)
2. Add the connector UUIDs to the trigger's mcp_connections
3. Run the trigger (manually or via cron)
4. The MCP tools are not available in the execution environment

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.89 (working on 31 March 2026, broken on 1 April 2026 — no version change between runs)

Claude Code Version

2.1.89

Platform

Other

Operating System

macOS

Terminal/Shell

Other

Additional Information

Platform: Claude Code remote triggers (claude.ai)
Terminal/shell: zsh

Connector details:

• Slack — UUID: 12a3b143-e10f-4d2d-aef8-a38c78533767, URL: https://mcp.slack.com/mcp
• Atlassian — UUID: 9e125e76-b649-44af-84c8-6ea7a7ee7378, URL: https://mcp.atlassian.com/v1/mcp

Troubleshooting already attempted:

• Updated all connector tool permissions to "always allow" — no effect
• Disconnected and reconnected both connectors in claude.ai — no effect
• Created a brand new remote trigger with the same connector UUIDs — same error

The fact that these connectors work in a local session but not in the remote trigger
environment points to the remote execution environment failing to inject OAuth credentials
at runtime.