Auto mode temporarily unavailable for MCP tools despite mcp__* in allow list

Resolved 💬 5 comments Opened Mar 25, 2026 by wcastand Closed May 2, 2026

Bug Description

MCP tool calls prompt for permission even though defaultMode is set to "auto" and mcp__* is in the allow list. The UI shows "auto mode temporarily unavailable" when an MCP tool is invoked.

Environment

  • Claude Code version: 2.1.83
  • OS: macOS (Darwin 25.3.0)
  • Shell: zsh

Settings

Both project (.claude/settings.json) and user (~/.claude/settings.json) have:

{
  "permissions": {
    "defaultMode": "auto",
    "allow": ["WebFetch", "WebSearch", "mcp__*", "Bash", "Read", "Skill"]
  },
  "enableAllProjectMcpServers": true
}

Steps to Reproduce

  1. Configure settings as shown above
  2. Have an MCP server configured (e.g., expo-mcp)
  3. Ask Claude to call an MCP tool (e.g., mcp__expo-mcp__read_documentation or mcp__expo-mcp__search_documentation)
  4. Claude Code shows "auto mode temporarily unavailable" and prompts for permission instead of auto-approving

Expected Behavior

MCP tool calls matching mcp__* should be auto-approved without prompting, consistent with the defaultMode: "auto" setting and the allow list.

Actual Behavior

Every MCP tool call triggers a permission prompt with the message "auto mode temporarily unavailable", regardless of whether the tool schema has been loaded via ToolSearch or not.

Notes

  • Non-MCP tools (Bash, Read, etc.) in the allow list work correctly in auto mode
  • The issue persists across conversation restarts
  • Tested with both deferred (not yet loaded) and fully loaded MCP tool schemas — both prompt for permission

View original on GitHub ↗

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