Scheduled CCR routines: MCP connectors requiring OAuth don't inject tools into remote session

Summary

MCP connectors configured in a scheduled routine's mcp_connections are not available as tools in the remote CCR session. ToolSearch returns No matching deferred tools found for connectors that work correctly in a local claude.ai session.

Steps to reproduce

1. Create a scheduled routine via RemoteTrigger with an MCP connector that requires OAuth (e.g. Linear at https://mcp.linear.app/mcp)
2. Authenticate the connector in your claude.ai session (OAuth flow completes successfully, tools are available locally)
3. Run the routine
4. Inside the remote session, call ToolSearch for any tool from that connector

Expected: The connector's tools are available in the remote session via ToolSearch

Actual: No matching deferred tools found — the connector is silently missing from the remote environment

Details

• Connector: Linear (https://mcp.linear.app/mcp)
• Connector UUID: fa50c30c-9f62-4f94-b851-217868185db6
• Environment: env_01Xfi33ByiJZXzNuELQnRo8F (Default, anthropic_cloud)
• Routine ID: trig_014Bd8bjGy1nB7s9xT6mCNMS
• Tested with both /mcp and /sse endpoints
• Tested after full OAuth re-authentication of the connector
• Notion and Slack MCP connectors work correctly in the same routine

Suspected cause

OAuth tokens acquired during the local claude.ai session are not being propagated to isolated CCR remote sessions. The connector is present in mcp_connections but the auth context needed to initialise its tools is missing in the remote environment.

Workaround attempted

Tried calling the Linear GraphQL API directly via curl in a Bash tool — blocked by CCR outbound network policy (api.linear.app is not in the allowlist).