few days ago I was able to work with Chrome DevTools MCP Server but it’s not working anymore. I provided Claude the logs and screenshot of the issue and it said this
Thanks for reporting this. We confirmed this is a compatibility issue between Katalon Studio’s current MCP client and Chrome DevTools MCP’s latest tool schema—not an issue with your Chrome or Node installation.
Chrome DevTools MCP now returns a valid JSON Schema format that Studio cannot currently parse, so the connection fails while loading tools. We’re tracking a permanent compatibility fix. In the meantime, we can provide a small compatibility wrapper as a workaround; please share your OS and current MCP server configuration (with any secrets removed), and we’ll send the exact setup steps.
Are we also planning for permanent fix to avoid compatibility issue?
I am using macOS 26.6.2 and here’s my Chrome DevTools MCP Server Config
STDIO - chrome-devtools-mcp
{
“command” : “npx”,
“args” : [ “-y”, “chrome-devtools-mcp@latest”, “–browserUrl=http://127.0.0.1:9222” ]
}
Please let me know if anything else is needed thanks @nghi.phan!!
Thanks for sharing your macOS version and MCP configuration. Please check that your actual Studio configuration uses straight quotation marks and two hyphens before
browserUrl(the version pasted here appears to have curly quotes and a single long dash). The URL should not include angle brackets:
json
> {"command":"npx","args":["-y","chrome-devtools-mcp@latest","--browserUrl=http://127.0.0.1:9222"]}
>
Save the configuration, restart Katalon Studio, and try again. If those characters were only changed when you pasted the configuration, or if the same
additionalProperties/tools/listerror persists, please let us know. That error indicates a compatibility issue between Studio’s MCP client and the Chrome DevTools MCP tool schema; it isn’t caused by your macOS version or browser URL. We can then provide a targeted compatibility workaround. If you see a different error, please paste its exact text (removing any secrets) so we can check it.
@manthanmevada quick workaround while katalon ships the fix: don’t use @latest. chrome-devtools-mcp released 1.10.0 and 1.10.1 on sep 23, which is right around when yours stopped working. pin the previous one in your config and restart studio:
{"command":"npx","args":["-y","chrome-devtools-mcp@1.9.0","--browserUrl=http://127.0.0.1:9222"]}
1.9.0 is from sep 8 so it should be the version you had when it was still working. also a good habit in general to pin mcp server versions, @latest means your studio setup can break overnight without you changing anything.