{"version":"2.1.265","anchor":"mcp-channel-flags-require-pluginserver-tagging","canonical_anchor":"mcp-channel-flags-require-pluginserver-tagging","heading":"MCP channel flags require plugin:\/server: tagging","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/mcp-channel-flags-require-pluginserver-tagging","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### MCP channel flags require plugin:\/server: tagging\n\n--channels and its development-channels flag now require explicit plugin: or server: tags\n\n**What**\n\nValues passed to the `--channels` flag and to `--dangerously-load-development-channels` must now be tagged, in the form `plugin:<name>@<marketplace>` or `server:<name>`. An entry without one of these tags is now rejected with an explicit error explaining the required formats.\n\n**Why**\n\nRequiring the tag removes ambiguity about whether a channel entry refers to a plugin or an MCP server, catching malformed flag values immediately instead of letting them silently fail or resolve incorrectly.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}