claude-code - 💡(How to fix) Fix Remote triggers with MCP connections prompt for tool approval despite always-allow setting

Description

Remote triggers (scheduled agents) using MCP connections (Microsoft 365) have stopped auto-approving tool calls. Each run now prompts "Allow Claude to use outlook email search," which blocks unattended execution and defeats the purpose of scheduled triggers.

Was working daily until ~May 20-21, 2026. No user-side configuration changes were made.

Current configuration

• Microsoft 365 connector set to "always allow" in claude.ai Customize settings
• Tools listed in both allowed_tools and permitted_tools on the trigger
• MCP connection properly configured with correct connector_uuid and URL

Observations

1. Tool naming convention changed from mcp__Microsoft-365__* to mcp__claude_ai_Microsoft_365__* — existing trigger configs referencing old names silently fail
2. After updating tool names, tools are found but still prompt for manual approval
3. Affects all triggers using the M365 MCP connection — three separate triggers (daily email summary, daily events scan, weekly recap) broke simultaneously
4. Connector "always allow" setting is not being respected in the remote trigger execution path

Expected behavior

MCP tools should auto-approve in remote triggers when the connector is set to "always allow" in claude.ai settings.

Actual behavior

Manual approval prompt appears on every MCP tool call, blocking unattended scheduled runs. The trigger outputs: "The tool calls require your approval — it looks like the Microsoft 365 MCP tools need to be authorized before they can run."

Impact

Scheduled triggers that depend on MCP connections are completely non-functional as unattended routines. There is no workaround — manual approval cannot be granted for scheduled runs.