claude-code - 💡(How to fix) Fix No way to configure MCP servers bundled with plugins [1 participants]

TL;DR

Customizing MCP server arguments for plugins is currently not supported, but a potential workaround could involve modifying the plugin's configuration or exploring alternative launch methods.

Guidance

• Investigate if the chrome-devtools-mcp plugin provides any internal configuration options or environment variables that could be used to customize the launch arguments.
• Consider reaching out to the plugin author or maintaining organization to request support for customizable MCP server arguments.
• If the plugin's MCP server launch mechanism is flexible, explore using a wrapper script or a custom launch command to pass the required --browserUrl argument.
• Review the priority and override rules for MCP servers to ensure correct understanding and application of these rules in the project's .mcp.json configuration.

Example

No code example is provided due to the lack of specific technical details about the plugin's internal configuration or launch mechanism.

Notes

The current implementation of MCP server argument customization is limited, and any workaround may require coordination with the plugin author or deeper investigation into the plugin's internal mechanics.

Recommendation

Apply workaround: Given the current limitations, exploring alternative launch methods or modifying the plugin's configuration seems to be the most viable approach to customize MCP server arguments for plugins.