docs: Add a note about previously installed server installations

[natorion]

No description provided.

[OrKoN]

@natorion please format the docs

[Sayvai]

@natorion / @OrKoN - If i were to remove my manual configuration of the MCP server configuration (and skills), how would i then be able to re-apply the custom arguments (e.g. --auto-connect, --no-usage-statistics, --acceptInsecureCerts) via the plugin installation route for the MCP (and Skills) installation via Claude Code plugins?

For example, here is my current manual Claude Code chrome-devtools MCP server configuration within .claude.json:

"chrome-devtools": {
  "command": "npx",
  "args": [
    "chrome-devtools-mcp@latest",
    "--acceptInsecureCerts",
    "--no-usage-statistics",
    "--auto-connect"
  ]
},

[OrKoN]

@Sayvai I believe even if installed as a plugin Claude keeps the configuration in the .claude.json in the user folder or in the global config. Unfortunately, it does not seem to provide any interface to edit the args except for editing the json file manually.

[Sayvai]

Thanks @OrKoN .

💡 Not sure whether it might be worth adjusting the README.md Claude section:

chrome-devtools-mcp/README.md

Lines 114 to 144 in 46bd54f

	<details>
	<summary>Claude Code</summary>
	**Install via CLI (MCP only)**
	Use the Claude Code CLI to add the Chrome DevTools MCP server (<a href="https://code.claude.com/docs/en/mcp">guide</a>):
	```bash
	claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest
	```
	**Install as a Plugin (MCP + Skills)**
	> [!NOTE]
	> If you already had Chrome DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.
	To install Chrome DevTools MCP with skills, add the marketplace registry in Claude Code:
	```sh
	/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
	```
	Then, install the plugin:
	```sh
	/plugin install chrome-devtools-mcp
	```
	Restart Claude Code to have the MCP server and skills load (check with `/skills`).
	</details>

to reflect the following nuances / caveats:

• to persist existing custom chrome-devtools argument(s) configuration (e.g. --auto-connect), you may install chrome-devtools via the Plugin marketplace, while not removing the existing configuration files.

🤔 However, this would contradict this current line in the README.md:

If you already had Chrome DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.

[Sayvai]

Looks like another user raised a separate similar issue relating to the limitation of adding custom MCP server arguments to plugin installed MCP servers in #1232