Remote triggers with OAuth MCP connectors (Gmail, Calendar) silently fail at runtime

Description

Remote triggers (scheduled agents) configured with OAuth-based MCP connectors from claude.ai (Gmail, Google Calendar) accept the configuration without errors but the MCP tools are not available to the agent at runtime.

Steps to Reproduce

1. Create a remote trigger via the RemoteTrigger API with mcp_connections pointing to OAuth connectors:

"mcp_connections": [
  {"connector_uuid": "...", "name": "Gmail", "url": "https://gmail.mcp.claude.com/mcp"},
  {"connector_uuid": "...", "name": "Google-Calendar", "url": "https://gcal.mcp.claude.com/mcp"}
]

1. Set allowed_tools: ["Bash", "Read", "Write", "Edit", "Glob", "Grep", "ToolSearch", "mcp__*"]
2. The API returns HTTP 200, trigger is created successfully
3. When the trigger runs, the remote agent cannot find any Gmail or Calendar MCP tools via ToolSearch

Expected Behavior

The remote agent should have access to the configured MCP connectors, or the API should return a validation error/warning if OAuth-based connectors are not supported in remote trigger environments.

Actual Behavior

• API accepts the configuration silently (HTTP 200)
• Trigger appears correctly configured in the UI with MCP connections listed
• At runtime, the agent reports: "Nenhuma tool MCP de Gmail ou Google Calendar foi encontrada neste ambiente. As integrações não estão conectadas a esta sessão de Claude Code."
• The agent falls back to suggesting manual MCP server setup

Environment

• Plan: Claude Max
• Environment: Default (anthropic_cloud)
• Connectors tested: Gmail (gmail.mcp.claude.com), Google Calendar (gcal.mcp.claude.com)
• Trigger IDs: trig_01WFCsu9oQnY13dg5RZCnbMZ (Morning Briefing), trig_01Nax8VhLG9iV7vrcV2P4Wj4 (Daily Wrapup)
• Both triggers have been running daily since 2026-03-31, consistently failing to connect MCP tools

Screenshot

The remote agent session shows it cannot find the MCP tools despite them being configured on the trigger.

Suggestion

Either:

1. Fix OAuth token propagation to remote trigger environments so connectors work as configured
2. Or validate at creation time and reject/warn when OAuth-based connectors are attached to triggers