What
Two separate lists now name mcp__ide__executeCode and mcp__ide__getDiagnostics as real constants where previously there were no-op placeholders, so these two IDE tools are special-cased somewhere in permission or tool-filtering.
Evidence
["mcp__ide__executeCode", "mcp__ide__getDiagnostics"]
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundlemcp__ide__executeCodemcp__ide__getDiagnostics
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up mcp__ide__executeCode, on Use Claude Code in VS Code.
| `mcp__ide__executeCode` | Runs Python code in the active Jupyter notebook's kernel. See confirmation flow below. | No |vs-code see the edit
Confirmed since
Anthropic's documentation has since written up mcp__ide__getDiagnostics, on JetBrains IDEs.
| `mcp__ide__getDiagnostics` | Returns the IDE's inspection diagnostics, the errors and warnings shown in the editor. Each call covers one file: the file Claude specifies, or the file in your active editor if Claude doesn't specify one. | …jetbrains see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up mcp__ide__getDiagnostics, on JetBrains IDEs.