{"version":"2.1.290","anchor":"plugin-mcp-type-restriction-message-split-marketplace-name","canonical_anchor":"plugin-mcp-type-restriction-message-split-marketplace-name","heading":"Clearer refusals for plugin MCP server types and marketplace names","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/plugin-mcp-type-restriction-message-split-marketplace-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer refusals for plugin MCP server types and marketplace names\n\nPlugins that declare a restricted MCP server type are now told which rule applies, and marketplace-name refusals give fix steps\n\n**Unclear.** It is not clear what condition decides when the reworded marketplace-name refusal is shown.\n\n**What**\n\nAn MCP server is an add-on, using the Model Context Protocol, that gives Claude extra tools. A plugin, a package that adds features to Claude Code, can declare its own MCP servers, but some server types are not allowed there. When a plugin declares one, Claude Code now says which rule it broke:\n\n- only the host app registers that type\n\n- only claude.ai connectors use that type\n\nBefore, only the first message existed.\n\nWhen Claude Code refuses a plugin marketplace because its name looks like one of Anthropic's own, the refusal now includes steps to fix it, including that removing it is the only fix.\n\n**Why**\n\nIf you hit one of these refusals, the message now tells you what went wrong and what to do about it.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}