An MCP server that controls a web browser directly. Used for web automation and real-browser verification and testing, including page navigation, clicking, typing, and screenshots.
Last 12 weeks · weekly buckets. New tools get more accurate as observation weeks add up.
Tools that are especially used together with this one. The higher the value, the better the fit.
browser MCP is an MCP server that controls a web browser directly. It is used for web automation and real-browser verification, including page navigation, clicking, typing, and screenshots.
Builders use it to open a web UI under development in a real browser and validate flows, or to hand repetitive browser actions to an agent. Per the summary, web automation and live-browser testing are the core use cases.
It is especially helpful when click paths and on-screen state must be checked before shipping. Direct browser control helps surface interaction issues that static HTML alone cannot reveal.
An MCP server that controls a web browser for automation and real-browser checks such as navigation, clicks, typing, and screenshots.
Verifying a web app's real behavior and automating repetitive browser actions during development.
They let an agent drive the browser to validate UI flows and capture screenshots before shipping.
It runs interactions in a live browser, so dynamic click paths and input results can be verified.