Fetch web pages using Chrome/Edge browser with auth, anti-bot, and JavaScript rendering support
Fetch web pages using Chrome/Edge browser with auth, anti-bot, and JavaScript rendering support. That is what the mcpbrowser mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Built on the Model Context Protocol (MCP), this web browser MCP server works seamlessly with Claude Desktop, Claude Code (CLI), GitHub Copilot, Kiro, Antigravity, and any MCP-compatible AI assistant. It handles corporate SSO, CAPTCHAs, Cloudflare protection, SPAs, dashboards, and any site that blocks automated requests. Your AI gets the same browser access you have — no special APIs, no headless browser detection, just your authenticated browser session.
Installation goes through your MCP client rather than a global install: point it at mcpbrowser on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 14 tools. What each one is for:
Cline — Follow the instruction in the section Configuring MCP ServersCodex — Alternatively, create or edit the configuration file ~/.codex/config.toml and add:Cursor — Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx -y mcpbrowser@latest. You can alsoFactory — Alternatively, type /mcp within Factory droid to open an interactive UI for managing MCP serversGoose — Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx -y mcpbrowser@latestKiro — Follow the MCP Servers documentation. For example in .kiro/settings/mcp.json:opencode — Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:OpenClaw — OpenClaw is a personal AI assistant that runs on your devices. Add MCPBrowser using the CLI:Warp — Go to Settings -> AI -> Manage MCP Servers -> + Add to add an MCP ServerWindsurf — Follow Windsurf MCP documentation. Use the standard config abovebrowser_fetch_webpage — Fetches web pages using your Chrome/Edge/Brave browser. Handles authentication, CAPTCHA, SSO, anti-bot protection, and JavaScript-heavy sites. Opensbrowser_execute_javascript — Executes a JavaScript snippet in the active page context and returns the result with metadata (execution time, truncation flag, URL-changePlenty 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. Mcpbrowser's toolset — Cline, Codex, Cursor and 11 more — is a fair guide to whether it matches your workflow. It is maintained by cherchyk; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Cline | Follow the instruction in the section [Configuring MCP Servers](https://docs.cline.bot/mcp/configuring-mcp-servers). |
| Codex | Alternatively, create or edit the configuration file ~/.codex/config.toml and add: |
| Cursor | Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx -y mcpbrowser@latest. You can also verify config or add command like arguments via clicking Edit. |
| Factory | Alternatively, type /mcp within Factory droid to open an interactive UI for managing MCP servers. |
| Goose | Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx -y mcpbrowser@latest. Click "Add Extension". |
| Kiro | Follow the MCP Servers [documentation](https://kiro.dev/docs/mcp/). For example in .kiro/settings/mcp.json: |
| opencode | Follow the MCP Servers [documentation](https://opencode.ai/docs/mcp-servers/). For example in ~/.config/opencode/opencode.json: |
| OpenClaw | [OpenClaw](https://openclaw.ai/) is a personal AI assistant that runs on your devices. Add MCPBrowser using the CLI: |
| Warp | Go to Settings -> AI -> Manage MCP Servers -> + Add to [add an MCP Server](https://docs.warp.dev/knowledge-and-collaboration/mcp#adding-an-mcp-server). Use the standard config above. |
| Windsurf | Follow Windsurf MCP [documentation](https://docs.windsurf.com/windsurf/cascade/mcp). Use the standard config above. |
| browser_fetch_webpage | Fetches web pages using your Chrome/Edge/Brave browser. Handles authentication, CAPTCHA, SSO, anti-bot protection, and JavaScript-heavy sites. Opens the URL in a browser tab (reuses existing tab for same domain) and wait |
| browser_execute_javascript | Executes a JavaScript snippet in the active page context and returns the result with metadata (execution time, truncation flag, URL-change detection). Use for structured data extraction (e.g., inbox rows) or JS-driven UI |
| browser_click_element | Clicks on any clickable element (buttons, links, divs with onclick handlers, etc.). Can target by CSS selector or visible text content. Automatically scrolls element into view and waits for page stability after clicking. |
| browser_type_text | Types text into one or more input fields in a single call. Supports filling entire forms at once for efficient automation. Automatically clears existing text by default. |
{
"mcpServers": {
"mcpbrowser": {
"command": "npx",
"args": ["-y", "mcpbrowser@latest"]
}
}
}Configuration as documented by the project. Restart the client after saving.
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.