What it does
The server controls the Chrome browser already installed on the user's machine. Each identity gets its own persistent browser profile, and the actions are exposed as Playwright MCP tools.
The publisher's description covers only this browser control and profile handling, so the entry does not specify particular workflows or use cases beyond that.
Running it requires Chrome to be installed locally. The source gives no further setup details.
Limitations and requirements
Requires Chrome to be installed on the local machine.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 16 Nov 2026 · last seen 16 Nov 2026 · its page on the source
io.github.william-monroy/turno-browser
Drives your installed Chrome with a persistent profile per identity (Playwright MCP tools).
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it