MCP server wildcard permission not working as documented

Resolved 💬 1 comment Opened Feb 5, 2026 by 207383-admin Closed Feb 5, 2026

According to the documentation at https://code.claude.com/docs/en/permissions#mcp, adding mcp__atlassian to the permissions.allow array should match ANY tool provided by the atlassian MCP server, similar to how the example shows mcp__puppeteer matching all tools from the puppeteer server.

However, despite having mcp__atlassian configured in ~/.claude/settings.json in the permissions.allow array, I'm still being prompted to approve individual tool calls from the atlassian-mcp-server.

Expected behavior

With mcp__atlassian in the allow list, all tools from the atlassian MCP server should be auto-approved without prompting.

Actual behavior

Still receiving prompts like:

Tool use
atlassian-mcp-server - Get issue(cloudId: "...", issueIdOrKey: "ABC-1234", ...) (MCP)
Get issue details

Do you want to proceed?
1. Yes
2. Yes, and don't ask again for atlassian-mcp-server - Get issue commands...
3. No

Configuration

{
  "permissions": {
    "allow": [
      "mcp__atlassian",
      ...
    ]
  }
}

The wildcard MCP permission matching doesn't appear to be working as documented.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗