Plugins with a bundled MCP server that needs setup now say so and point to Configure

What

An MCP server is a helper program that gives Claude extra tools. Some plugins bundle one as an .mcpb package, and it may need settings, such as a key, before it can run. Claude Code now treats this as its own state, mcpb-needs-config, instead of failing quietly:

• Skip message: "Bundled MCP server was not started: it needs configuration."
• New hint: a bundled MCP server needs configuration before it can start, with directions to the plugin's Installed tab in /plugin and its Configure option.
• Plugin error list: a new mcpb-needs-config error says to open the plugin in the Installed tab and choose Configure. It is listed once per server name, and it now comes with an action to fix it. Before, these errors had no action.
• Warning record: a plugin whose bundled server needs setup now records a warning that names the skipped server. Before, only a debug log line existed, and it pointed to /plugin → Manage plugins. The path given is now /plugin → Installed → plugin → Configure.
• Install and enable messages: a needs-config result now shows "Plugin is now active." followed by an extra note. Before, it fell through to "Run /reload-plugins to activate."
• Plugin refresh: now returns a needs_config status when this warning applies to a plugin.

In the same area, the rules that allow or block MCP servers by policy gained extra checks. They now also look at servers given by URL and at servers that come from plugins.

Why

Before, a plugin could install fine while its bundled server simply never started, with no visible reason. Now you are told which server was skipped and where to fill in its settings, and the install message no longer suggests reloading when setup is what is missing.