pw-mcp
It enables each agent session to have its own isolated Chrome browser with a persistent profile, avoiding profile-lock conflicts and shared tab spaces, while resumed sessions reattach to the same browser and tabs. It can also seed new sessions with a saved login template so they start signed in.
- Score
- Unranked
- Evidence
- No signals yet
- Last commit
- as last read from GitHub; most reads are from 2 Sep 2026 or later
- Listed
Install
No one-command install. Set it up from its source.
Alternatives · MCPs
- asynkor50 stars · 2 forks79.176
- chromeboost8 stars · 1 fork59.029
- ultimate-playwright-mcp3 stars · 3 forks52.443
What it is
It enables each agent session to have its own isolated Chrome browser with a persistent profile, avoiding profile-lock conflicts and shared tab spaces, while resumed sessions reattach to the same browser and tabs. It can also seed new sessions with a saved login template so they start signed in.
When to use it
It enables each agent session to have its own isolated Chrome browser with a persistent profile, avoiding profile-lock conflicts and shared tab spaces, while resumed sessions reattach to the same browser and tabs. It can also seed new sessions with a saved login template so they start signed in.
How to install / invoke
See Glama for the install config.
Notes
Listed from the Glama MCP registry.