Remote Trigger (Scheduled Agent): MCP cloud connectors not loaded in execution environment
Resolved 💬 1 comment Opened Apr 2, 2026 by TatsukiSatoh Closed Apr 2, 2026
Bug Description
MCP cloud connectors (Slack, Notion) specified in Remote Trigger mcp_connections are not being loaded in the execution environment. Only MCP servers defined in the repository's .mcp.json are available.
Environment
- Claude Code CLI (macOS)
- Remote Triggers (Scheduled Agents) via
claude.ai
Steps to Reproduce
- Create a Remote Trigger with
mcp_connectionsreferencing cloud connectors (e.g., Slack, Notion):
``json``
"mcp_connections": [
{"connector_uuid": "xxx", "name": "notion", "url": "https://mcp.notion.com/mcp"},
{"connector_uuid": "xxx", "name": "Slack", "url": "https://mcp.slack.com/mcp"}
]
- The trigger also references a git repository source that has a
.mcp.jsonwith other MCP servers (e.g.,context7,deepwiki). - Run the trigger (either scheduled or manual via API).
Expected Behavior
The execution environment should have access to:
- MCP servers from the repository's
.mcp.json(e.g., context7, deepwiki) - MCP cloud connectors from
mcp_connections(e.g., Slack, Notion)
Actual Behavior
Only MCP servers from the repository's .mcp.json are loaded:
- ✅
context7(from.mcp.json) — available - ✅
deepwiki(from.mcp.json) — available - ❌ Slack cloud connector — not available
- ❌ Notion cloud connector — not available
The agent reports:
Slack・NotionのMCPツールがこの環境に設定されていません。現在利用可能なMCPサーバーは以下のみです: context7, deepwiki
Additional Context
- This was working until 2026-03-31. The same trigger successfully used Slack and Notion MCP connectors daily from 2026-03-24 to 2026-03-31.
- Broke on 2026-04-01. No configuration changes were made on our side.
- Connectors are properly authorized in
claude.ai/settings/connectors. - Newly created triggers with the same connector configuration also fail — this is not specific to old triggers.
- The trigger's
enabledfield istrueandnext_run_atis correctly scheduled. - Manual runs via
POST /v1/code/triggers/{id}/runalso reproduce the issue.
Workaround
Currently running the same task locally via Claude Code CLI where MCP connectors work correctly.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗