Plugin mode: support --browserUrl via pluginConfigs

Problem

When using chrome-devtools-mcp as a Claude Code plugin (chrome-devtools-mcp@claude-plugins-official), the MCP server is launched as:

npx chrome-devtools-mcp@latest

There is no way to pass --browserUrl http://127.0.0.1:9222 (or other CLI flags) through the plugin configuration system. This means the plugin cannot connect to an existing Chrome instance with remote debugging enabled.

Current workaround

Disable the plugin and configure a standalone MCP server in .mcp.json:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["chrome-devtools-mcp@latest", "--browserUrl", "http://127.0.0.1:9222"]
    }
  }
}

This works for tools, but loses the plugin's bundled skills (a11y-debugging, debug-optimize-lcp, chrome-devtools, troubleshooting).

Proposed solution

Support --browserUrl (and potentially other CLI flags like --autoConnect, --channel) as user-configurable options through Claude Code's pluginConfigs mechanism in settings.json:

{
  "pluginConfigs": {
    "chrome-devtools-mcp@claude-plugins-official": {
      "mcpServers": {
        "chrome-devtools": {
          "browserUrl": "http://127.0.0.1:9222"
        }
      }
    }
  }
}

This would allow users to connect to an existing Chrome instance while retaining the plugin's skills.

Environment

• OS: Windows 11
• Claude Code plugin: chrome-devtools-mcp@claude-plugins-official
• chrome-devtools-mcp version: 0.19.0
• Chrome remote debugging enabled on 127.0.0.1:9222

Start by tracing how Claude Code's pluginConfigs reaches the MCP server and how the existing --browserUrl, --autoConnect, and --channel options are parsed. Define done as allowing browserUrl through the shown pluginConfigs shape while preserving the bundled skills, with coverage for connecting to an existing Chrome instance.