Remote trigger MCP connectors not loading - tools unavailable in remote sandbox

Resolved 💬 3 comments Opened Apr 1, 2026 by rshields80 Closed Apr 10, 2026

Bug Description

Remote trigger (scheduled agent) cannot discover or load MCP connector tools in the remote sandbox. The agent attempts to find tools via ToolSearch but gets "No matching deferred tools found" for all connected MCP services. The agent then gives up with "The required MCP-connected tools are not available in this environment."

Setup

  • Trigger ID: trig_017Vc7g9ysZdwMKwxqK7WvTd
  • - Environment: env_018ZRzmzWSjHKKN82p98rZyk (anthropic_cloud)
  • - - Model: claude-sonnet-4-6
  • - - - MCP connectors attached to trigger: Atlassian Rovo, Microsoft 365, Slack
  • - - - - All three connectors show as connected in https://claude.ai/settings/connectors

Expected Behavior

The remote agent should be able to discover and call MCP tools from the attached connectors (e.g. searchJiraIssuesUsingJql, outlook_email_search, slack_send_message).

Actual Behavior

The remote agent uses ToolSearch to look for the MCP tools and gets "No matching deferred tools found" for every search (jira, outlook, slack, etc.). Tested with both broad keyword searches and exact select: prefixed names. The agent cannot find any MCP tools at all.

Reproduction

  1. Create a remote trigger with MCP connectors attached (Atlassian Rovo, Microsoft 365, Slack)
  2. 2. Run the trigger
  3. 3. Agent cannot find any MCP tools via ToolSearch or direct invocation

Tested with ToolSearch in allowed_tools and without. Same failure both ways.

Key Detail

This same trigger with the same prompt and same connectors worked successfully on 3/31/2026. It stopped working on 4/1/2026 with no changes to the trigger configuration. Multiple manual runs via RemoteTrigger API on 4/1 all failed the same way.

Environment

  • Platform: Windows 11 Pro
  • - Claude Code version: latest
  • - - Trigger managed via RemoteTrigger API and claude.ai/code/scheduled

View original on GitHub ↗

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