CCR: MCP connector tools not found in ToolSearch on session start

Bug Description

When a scheduled trigger (CCR - Claude Code Remote) starts a new session, MCP connector tools (Linear, Gmail, Slack) are not immediately available via ToolSearch. The agent searches for them, gets 0 results, and gives up — reporting that MCP tools are not configured.

However, if the user manually intervenes in the session by saying something like "the connectors are shown right here, why can't you use them?" (sometimes with a screenshot of the connector panel), ToolSearch suddenly finds the tools and the agent proceeds normally.

Environment

• Trigger ID: trig_01DKEzSh51AhaHbrzFW1JY2S
• Environment: env_01Ct3JCqk4u59S8J6Hb3uJAm (Anthropic Cloud)
• Model: claude-sonnet-4-6
• MCP Connections: Gmail, Slack, Linear (all configured in trigger's mcp_connections)

Steps to Reproduce

1. Create a scheduled trigger with MCP connectors (e.g., Linear, Gmail, Slack)
2. Run the trigger (either via cron or "Run now")
3. The agent starts and calls ToolSearch({query: "linear", max_results: 20})
4. ToolSearch returns 0 results — only built-in tools (WebFetch, WebSearch, TodoWrite, etc.) are found
5. The agent concludes MCP tools are not available and stops

Expected Behavior

MCP connector tools should be immediately available via ToolSearch when a CCR session starts, since they are explicitly configured in the trigger's mcp_connections.

Actual Behavior

ToolSearch returns 0 results for MCP connector tools on initial attempts. The tools appear to load with a delay (sometimes 10-30+ seconds after session start).

Workarounds Attempted

• Adding sleep 5 / sleep 10 before ToolSearch retry — sometimes works, sometimes doesn't
• Prompt instructions saying "retry 3 times with sleep" — agent sometimes still gives up
• Prompt instructions saying "tools are already connected, don't check config" — agent still runs ToolSearch and finds nothing
• Manual intervention in the session (typing "the connectors are right there") — this reliably works, suggesting the tools do load eventually

Suggestion

It would help if either:

1. MCP connector tools were pre-loaded before the first user message is processed
2. ToolSearch had a built-in retry/wait mechanism for MCP connectors
3. There was a way to specify in the trigger config that MCP tools should be loaded synchronously before the session starts