ChromeDevTools
Stealth mode to circumvent bot detection
Being Blocked by bot detection.
Till date I was using this MCP server programatically with open ai agents SDK to create an AI agent.
I avoided bot detection while running in headless with the following config -
"mcpServers": { "chrome-devtools": { "command": "npx -y chrome-devtools-mcp@latest", "env": {}, "args": [ "--headless=true", "--isolated=true", "--viewport=1280x900", "--chromeArg=--disable-blink-features=AutomationControlled", "--chromeArg=--user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" ] }
But now those websites have updated their bot measures and even with "--headless=false" this config triggers a bot response.
Describe the solution you'd like
ZFC Digital's puppeteer-real-browser package is stealthy and avoids bot triggers.
So is there any way to get the mcp server to use/rely on that package to avoid bot detection? Or is there any other way to configure the chromedevtools mcp server to avoid bot measures?
Any advice is greatly appreciated.
Describe alternatives you've considered
There is another mcp literally called the puppeteer-real-browser-mcp-server which does not trigger bot measures but is not as reliable as the ChromeDevTools mcp.
Additional context
No response
No it is not
On Fri, Nov 14, 2025, 6:39 PM Bharath A. Irukulapati < @.***> wrote:
ibac03 created an issue (ChromeDevTools/chrome-devtools-mcp#553) https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/553 Is your feature request related to a problem? Please describe.
Till date I was using this MCP server programatically with open ai agents SDK to create an AI agent.
I avoided bot detection while running in headless with the following config -
"mcpServers": { "chrome-devtools": { "command": "npx -y @.***", "env": {}, "args": [ "--headless=true", "--isolated=true", "--viewport=1280x900", "--chromeArg=--disable-blink-features=AutomationControlled", "--chromeArg=--user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" ] }
But now those websites have updated their bot measures and even with "--headless=false" this config triggers a bot response. Describe the solution you'd like
ZFC Digital's puppeteer-real-browser package is stealthy and avoids bot triggers.
So is there any way to get the mcp server to use/rely on that package to avoid bot detection? Or is there any other way to configure the chromedevtools mcp server to avoid bot measures?
Any advice is greatly appreciated. Describe alternatives you've considered
There is another mcp literally called the puppeteer-real-browser-mcp-server which does not trigger bot measures but is not as reliable as the ChromeDevTools mcp. Additional context
No response
— Reply to this email directly, view it on GitHub https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/553, or unsubscribe https://github.com/notifications/unsubscribe-auth/BYGGH4YIPQZOIRZKK65OG4T34Z74DAVCNFSM6AAAAACMFPBJU6VHI2DSMVQWIX3LMV43ASLTON2WKOZTGYZDONZVGU2TINI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
You asked if my response was due to a problem. I said it was not due to a problem. More excitement than anything
On Fri, Nov 14, 2025, 8:07 PM Bharath A. Irukulapati < @.***> wrote:
ibac03 left a comment (ChromeDevTools/chrome-devtools-mcp#553) https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/553#issuecomment-3535482855
I am sorry, I don't understand what you mean.
— Reply to this email directly, view it on GitHub https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/553#issuecomment-3535482855, or unsubscribe https://github.com/notifications/unsubscribe-auth/BYGGH45VV5BXXWXQ2B4RAFL342KH7AVCNFSM6AAAAACMFPBJU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZVGQ4DEOBVGU . You are receiving this because you commented.Message ID: @.***>
Right now we don't plan to add mechanisms to avoid bot detection. I will keep this feature request open to collect related feedback in here.
This would be an incredible feature to have. The ChromeDevTools MCP is wonderfully stable, and being able to pair that reliability with something as stealthy as puppeteer-real-browser would unlock a whole new tier of usability. Right now there’s a bit of a no-man’s-land between reliability and evasion, so anything that bridges that gap would be a huge step forward.
Thanks for raising this, and I hope this becomes possible soon.
I use the server too, and this feature would be extremely helpful for me as well.
cc @natorion any update on this? there seems to be some interest in this feature.
If you are not able to add full fledged stealth features immediately, atleast giving an option to connect to 3rd party stealth browser options via their api, for eg., connecting to bright data's stealth web browser api, would still be very useful.