ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Stealth mode to circumvent bot detection
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the MCP server configuration and the listed Chrome launch arguments, then compare the requested integration with ZFC Digital's puppeteer-real-browser package and the puppeteer-real-browser-mcp-server alternative. Determine whether a supported configuration or integration path is defined; done should include a clearly documented, maintainable approach rather than an ad hoc stealth workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100