No way to configure MCP servers bundled with plugins

Problem

There is no way to customize the arguments of MCP servers that come bundled with plugins. The only option is to hack the cached .mcp.json inside ~/.claude/plugins/cache/, which gets overwritten on plugin updates.

Example

The chrome-devtools-mcp plugin ships an MCP server that tries to launch a local Chrome. In my setup, Chrome runs on a remote machine and is accessible via --browserUrl http://127.0.0.1:9222. I have no way to pass this argument to the plugin's MCP server.

I tried adding a same-named server in the project .mcp.json with the correct arguments, expecting it to override the plugin's version per the documented priority rules. It didn't — both servers coexist with different prefixes (mcp__chrome-devtools__ vs mcp__plugin_chrome-devtools-mcp_chrome-devtools__), so the override never happens.

Expected

Either:

• Allow users to override plugin MCP server arguments (e.g. via settings.json or .mcp.json)
• Or make the priority/override mechanism actually merge same-named servers across scopes