What's wrong with this entry?
A new --plugin-dir-no-mcp flag that loads a plugin directory without also reading its .mcp.json file. Useful when the SDK host already owns and manages the plugin's MCP connections.
claude --plugin-dir-no-mcp <path>- Behaves exactly like
--plugin-direxcept the engine skips.mcp.json/mcpServersdiscovery for that plugin - Equivalent behavior is also available as a setting:
noMcp: truein the plugin frontmatter - Intended for SDK hosts that register MCP servers themselves rather than delegating to the engine
New flag definition and help text (search for "Like --plugin-dir but the engine will not read this plugin's .mcp.json")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.