Remote triggers: MCP connections configured but tools not available at runtime

Resolved 💬 3 comments Opened Apr 2, 2026 by adrientaravant Closed Apr 6, 2026

Bug description

MCP connections added to remote triggers (scheduled agents) are not available at runtime. The tools cannot be discovered via ToolSearch, and the agent has no way to use the configured MCPs.

Steps to reproduce

  1. Create a remote trigger via API or UI at https://claude.ai/code/scheduled
  2. Add MCP connections (e.g., Slite MCP, Linear, Super MCP) — the UI allows this
  3. Run the trigger
  4. The agent tries ToolSearch with various queries to find MCP tools → no matching deferred tools found
  5. Agent falls back to WebFetch on the MCP API URLs directly → gets 403 (auth required)

Evidence

Two separate triggers exhibit the same behavior:

Trigger 1: notion-api-monitor (trig_01CaRsV3A77VXDeBsAapKMkM)

  • MCP configured: Slite (11273c32-c059-4198-a2b6-2a5f2910fdff)
  • ToolSearch "Slite" → no results
  • Agent output: "No Slite MCP tools are available in this environment"

Trigger 2: sanity-content-sync (trig_01DhvUvG6n8E911EuUVnnpa1)

  • MCPs configured: Slite + Sanity
  • ToolSearch "slite note collection create" → no matching deferred tools
  • ToolSearch "get-note create-note slite" → no matching deferred tools
  • ToolSearch "sanity groq query" → no matching deferred tools
  • Agent falls back to WebFetch on Sanity API → 403

Screenshots

The agent searches for tools, finds nothing, and falls back to direct HTTP calls which fail:

ToolSearch  slite note collection create
ToolSearch  sanity groq query       → No matching deferred tools found
ToolSearch  get-note create-note slite  → No matching deferred tools found
ToolSearch  note collection channel

WebFetch https://dnsgqii5.api.sanity.io/... → Request failed with status code 403
WebFetch https://api.slite.com/v1/notes/... → Request failed with status code 403

Expected behavior

MCP tools configured in the trigger's mcp_connections should be available as deferred tools (discoverable via ToolSearch) or directly callable in the remote trigger execution environment.

Environment

  • Trigger API version: v1 (auto-translated to v2)
  • Environment ID: env_01CMW7CJd6aNKPooy8CE1qKA
  • Model: claude-sonnet-4-6 and claude-opus-4-6[1m] (both affected)

🤖 Generated with Claude Code

View original on GitHub ↗

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