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.
Usage
claude --plugin-dir-no-mcp <path>
Details
Behaves exactly like --plugin-dir except the engine skips .mcp.json / mcpServers discovery for that plugin
Equivalent behavior is also available as a setting: noMcp: true in the plugin frontmatter
Intended for SDK hosts that register MCP servers themselves rather than delegating to the engine
Evidence
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.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed background agents potentially reading another directory's project settings (.mcp.json approvals, trust) when dispatched onto a…
