The Web Browser MCP Server provides AI models with the ability to browse websites, extract content, and understand web pages through the Message
Web Browser MCP server exists for a simple reason — assistants are far more useful when they can act on Web Browser directly instead of describing what you should do. The Web Browser MCP Server provides AI models with the ability to browse websites, extract content, and understand web pages through the Message Control Protocol (MCP). It enables smart content extraction with CSS selectors and robust.
Once Web Browser is connected, these are the calls the assistant has available:
browse_webpage — Browse and extract content from web pages with optional CSS selectors:You will need one environment variable: REQUEST_TIMEOUT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Web Browser's toolset — browse_webpage — is a fair guide to whether it matches your workflow. It is maintained by blazickjp; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| browse_webpage | Browse and extract content from web pages with optional CSS selectors: |
{
"mcpServers": {
"web-browser-mcp-server": {
"command": "uv",
"args": [
"tool",
"run",
"web-browser-mcp-server"
],
"env": {
"REQUEST_TIMEOUT": "30"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| REQUEST_TIMEOUT | Configuration value read at startup. | Optional |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.