Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why use this over Puppeteer or Playwright extensions?


The Puppeteer MCP server doesn't work well because it requires CSS selectors to interact with elements. It makes up CSS selectors rather than reading the page and generating working selectors.

The Playwright MCP server is great! Currently Browser MCP is largely an adaptation of the Playwright MCP server to use with your actual browser rather than creating a new one each time. This allows you to reuse your existing Chrome profile so that you don't need to log in to each service all over again and avoids bot detection which often triggers when using the fresh browser instances created by Playwright.

I also plan to add other useful tools (e.g. Browser MCP currently supports a tool to get the console logs which is useful for automated debugging) which will likely diverge from the Playwright MCP server features.


by the way, you can indeed access your personal context with Playwright. just `launchPersistentContext()` and set the userDataDir to that of your existing Chrome install:

https://playwright.dev/docs/api/class-browsertype#browser-ty...


Ooo, i like that. one of the most annoying points has been 'not sharing' the browser context. i'll def check it out




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: