[Bug] MCP connectors unavailable in remote trigger environments

Resolved 💬 4 comments Opened Apr 7, 2026 by sweetyclem Closed May 20, 2026

Bug Description
MCP connectors (Notion, Slack) don't load in remote trigger environments. Triggers fire on schedule but the agent only has access to base tools (Read, Write, Bash, WebSearch, etc), no MCP tools appear at all. Confirmed by checking the "Loaded tools" and agent output in run history. Reproduced across multiple attempts: re-attaching connectors in the UI, creating a brand new trigger from scratch, setting all Notion tool permissions to "Always allow". Same result every time, the MCP server never connects. The same connectors work fine in interactive Claude Code sessions (both CLI and web).

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.1.92
  • Feedback ID: efc016ad-829e-48c1-84f8-2df42e7d1df4

<img width="724" height="424" alt="Image" src="https://github.com/user-attachments/assets/b2c55e57-9ee5-4053-9a02-cadc7a190401" />

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗