[BUG] Playwright plugin ignores .mcp.json args — hardcodes --headless only

Resolved 💬 2 comments Opened Feb 18, 2026 by richard-scott Closed Feb 18, 2026

Bug Description

When the Playwright MCP plugin is installed via the Claude Code plugin marketplace, Claude Code hardcodes the launch command as:

\\\
npm exec @playwright/mcp@latest --headless
\
\\

It ignores the \args\ array defined in the plugin's \.mcp.json\ file. Any additional arguments added to the config (e.g. \--ignore-https-errors\) are silently dropped.

Environment

  • OS: Linux 6.17.0-14-generic
  • Claude Code Version: latest
  • Plugin: \playwright@claude-plugins-official\

Steps to Reproduce

  1. Install the Playwright plugin from the official Claude Code marketplace
  2. Edit \~/.claude/plugins/marketplaces/claude-plugins-official/external_plugins/playwright/.mcp.json\ to add an extra arg:

\\\json
{
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest", "--ignore-https-errors"]
}
}
\
\\

  1. Restart Claude Code
  2. Check the running process: \ps aux | grep playwright-mcp\

Expected Behaviour

The MCP server should launch with all args from the config:
\\\
npm exec @playwright/mcp@latest --headless --ignore-https-errors
\
\\

Actual Behaviour

The process launches with only \--headless\, ignoring the extra arg:
\\\
npm exec @playwright/mcp@latest --headless
\
\\

Impact

There is no supported way to pass additional flags to the Playwright MCP server when using the plugin. Workarounds like \settings.json\ \mcpServers\ or \pluginConfigs\ do not apply to plugin-managed MCP servers. This makes it impossible to use Playwright MCP with self-signed TLS certificates in local development environments (requires \--ignore-https-errors\).

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗