News for hackers. Stuff that matters.
Re:Show HN: Browser MCP – Automate your browser using Cursor... by rahimnathwani on Monday April 07, 2025 @01:24PM (#43613833)
This is cool. I'm curious why you chose to use an extension, rather than getting the user to run Chrome with remote debugging turned on?
Re:Show HN: Browser MCP – Automate your browser using Cursor... by namukang on Monday April 07, 2025 @01:36PM (#43613934)
An extension is more user-friendly! I leave Chrome open basically 24/7 and having to create a new Chrome instance via the command line just to use Browser MCP just felt like too high of a barrier.
Re:Show HN: Browser MCP – Automate your browser using Cursor... by hannofcart on Monday April 07, 2025 @01:34PM (#43613912)
Not OP but I suspect it is because of this (mentioned on their page):

'Avoids bot detection and CAPTCHAs by using your real browser fingerprint.'

Re:Show HN: Browser MCP – Automate your browser using Cursor... by tylergetsay on Monday April 07, 2025 @01:35PM (#43613929)
I don't think remote debugging by itself on a normal chrome profile is detectable
Re:Show HN: Browser MCP – Automate your browser using Cursor... by omneity on Monday April 07, 2025 @03:02PM (#43614737)
Exposing Chrome CDP is a terrible idea from a security and privacy perspective. You get the keys to the whole kingdom (and expose them on a standard port with a well documented API). All security features of the web can be bypassed, and then some, as CDP exposes even more capabilities than chrome extensions and without any form of supervision.
Re:Show HN: Browser MCP – Automate your browser using Cursor... by redblacktree on Monday April 07, 2025 @05:05PM (#43615940)
You're talking about exposing Chrome CDP to the wider internet, right? Or are you highlighting these dangers in the local context?
Re:Show HN: Browser MCP – Automate your browser using Cursor... by omneity on Monday April 07, 2025 @07:27PM (#43616964)
In the local context as well. Unlike say the docker socket which is protected by default using unix permissions, the CDP protocol has no authorization, authentication or permission mechanism.

Anything on your machine (such as a rogue browser extension or a malicious npm/pypi package) could scan for this and just get all your cookies - and that's only the beginning of your problems.

CDP can access any origin, any data stored (localStorage, indexedDB ...), any javascript heap, cross iframe and origin boundaries, run almost undetectable code that uses your sessions without you knowing, and the list is very long. CDP was never meant to expose a real browser in an untrusted context.

Re:Show HN: Browser MCP – Automate your browser using Cursor... by parhamn on Monday April 07, 2025 @01:42PM (#43613998)
I'm sure its about the cookies/sessions but I do recall you can load cookies from another browser?