{"version":"2.1.172","anchor":"plugin-dir-no-mcp-flag","canonical_anchor":"plugin-dir-no-mcp-flag","heading":"--plugin-dir-no-mcp Flag","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.172\/e\/plugin-dir-no-mcp-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.172","markdown":"### --plugin-dir-no-mcp Flag\n\n**What**\n\nA 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.\n\n**Usage**\n\n`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\"`)"}