Authenticated pages

[lebreRafael]

Is there any guidance on how to deal with authenticated pages?

I think the ideal scenario would be some sort of config where we could set a cookie to be used by the chrome session opened by the MCP.
Maybe for now until we get something like that we can add instructions to our AI tool to go to the login page of our app and authenticate using some test credentials. The downside is that I believe it would need to authenticate for every new chrome session the MCP opens, which could be slow and resource consuming.

btw, thanks for the team working on this MCP. I believe it's gonna help a lot

[fnlearner]

when I login manually I type 'try again ' and it will continue to test

[natorion]

--auto-connect is likely the solution you are looking for. see https://github.com/ChromeDevTools/chrome-devtools-mcp#configuration

[esokullu]

Adding a note for anyone landing here later: the tradeoff with a CDP-driven setup is that you're either launching a fresh profile or attaching to an existing Chrome, and each has its own auth headaches (separate profile = re-login; attaching = you're driving your real session, which you may or may not want).

An alternative shape is running the agent as a browser extension instead — it operates inside the session you're already in, so authenticated pages and 2FA-gated flows just work, no profile or cookie plumbing. That's the approach we took with WebBrain (open source, MIT): https://github.com/webbrain-one/webbrain — different tradeoffs, not a drop-in replacement for what this MCP does.