Browser

✅ MCPBrowser (MCP Browser)

⚠️ Security Notice: MCPBrowser extracts webpage content and provides it to your AI agent (e.g., GitHub Copilot, Claude, Kiro, Antigravity), which then sends it to the LLM provider it uses (e.g., Anthropic, OpenAI, GitHub) for processing. Make sure you trust both your agent and the LLM provider — especially when accessing pages with sensitive or private data. MCPBrowser combines private data access, untrusted content exposure, and external communication (the MCP "lethal trifecta") — all tool annotations accurately declare these risks so MCP clients can enforce appropriate safety controls. See MCPBrowser/docs/MCP_COMPLIANCE.md for details.

💡 Why MCPBrowser over Puppeteer/Playwright MCP servers? Puppeteer and Playwright are browser automation libraries — their MCP servers give agents raw, low-level browser commands. MCPBrowser uses Puppeteer under the hood and was built specifically for AI agents, adding an intelligence layer that handles the hard parts automatically.

The agent gets clean HTML (90% smaller), automatic SPA detection (React, Vue, Angular), authentication flow handling (SSO, redirects, multi-step login), form discovery with multi-field filling, structured responses with next-step guidance, domain-based tab reuse, and instant DOM re-extraction without page reloads. Each MCPBrowser tool call replaces 5-8 raw browser automation calls — a typical 4-step workflow in MCPBrowser would take 20+ calls with Puppeteer/Playwright MCP, saving tokens and making the agent significantly faster. See full comparison below.

MCPBrowser is an MCP browser server that gives AI assistants the ability to browse web pages using a real Chrome, Edge, or Brave browser. This browser-based MCP server lets AI assistants (Claude, Copilot, Kiro, Antigravity) access any website — especially those protected by authentication, CAPTCHAs, anti-bot restrictions, or requiring JavaScript rendering. Uses your real browser session for web automation, so you log in once, and your AI can navigate, click buttons, fill forms, and extract content from sites that block automated requests.

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.

Example workflow for AI assistant to use MCPBrowser

1. browser_fetch_webpage    → Load the login page

1. browser_type_text → Enter username & password (multiple fields at once)
2. browser_click_element → Click "Sign In"
3. browser_get_current_html → Extract the content after login

Contents

• Why MCPBrowser over Puppeteer/Playwright MCP servers?
• Requirements
• Installation
• Amp
• Claude Code
• Claude Desktop
• Cline
• Codex
• Copilot CLI
• Cursor
• Factory
• Gemini CLI
• Goose
• Kiro
• LM Studio
• opencode
• OpenClaw
• Qodo Gen
• VS Code (GitHub Copilot)
• VS Code Extension
• Warp
• Windsurf
• MCP Tools
• browser_fetch_webpage
• browser_execute_javascript
• browser_click_element
• browser_type_text
• browser_get_current_html
• browser_scroll_page
• browser_take_screenshot
• browser_close_tab
• CLI Mode
• Configuration
• Troubleshooting
• For Developers
• Links
• License

Requirements

• Chrome, Edge, or Brave browser
• Node.js 18+ (includes npm)

Note: Node.js must be installed on your system. The VS Code extension and npm package both require Node.js to run the MCP server. Download from nodejs.org if not already installed.

Why MCPBrowser over Puppeteer/Playwright MCP servers?

Puppeteer and Playwright are browser automation libraries — their MCP servers expose low-level browser commands and the agent has to handle SPAs, auth flows, messy HTML, and edge cases on its own. MCPBrowser was built specifically for AI agents. It uses Puppeteer under the hood and adds an intelligence layer so the agent can focus on the task instead of fighting the browser.

Installation

Getting started

First, install MCPBrowser with your MCP client.

Standard config works in most tools:

{

"mcpServers": { "mcpbrowser": { "command": "npx", "args": ["-y", "mcpbrowser@latest"] } } }

---

Amp

Add via the Amp VS Code extension settings screen or by updating your settings.json file:

"amp.mcpServers": {

"mcpbrowser": { "command": "npx", "args": ["-y", "mcpbrowser@latest"] } }

Amp CLI Setup:

amp mcp add mcpbrowser -- npx -y mcpbrowser@latest

---

Claude Code

Use the Claude Code CLI to add the MCPBrowser MCP server:

claude mcp add mcpbrowser --scope user -- npx -y mcpbrowser@latest

Verify it's working:

claude mcp list

You should see:

mcpbrowser: npx -y mcpbrowser@latest - ✓ Connected

---

Claude Desktop

Add to your config file (create it if it doesn't exist):

Windows: %APPDATA%\Claude\claude_desktop_config.json (e.g., C:\Users\ \AppData\Roaming\Claude\claude_desktop_config.json) Mac: ~/Library/Application Support/Claude/claude_desktop_config.json

{

"mcpServers": { "mcpbrowser": { "command": "npx", "args": ["-y", "mcpbrowser@latest"] } } }

Restart Claude Desktop after saving.

---

Cline

Follow the instruction in the section Configuring MCP Servers.

Add the following to your cline_mcp_settings.json file:

{

"mcpServers": { "mcpbrowser": { "type": "stdio", "command": "npx", "timeout": 30, "args": ["-y", "mcpbrowser@latest"], "disabled": false } } }

---

Codex

Use the Codex CLI to add the MCPBrowser MCP server:

codex mcp add mcpbrowser npx "-y" "mcpbrowser@latest"

Alternatively, create or edit the configuration file ~/.codex/config.toml and add:

[mcp_servers.mcpbrowser]

command = "npx" args = ["-y", "mcpbrowser@latest"]

For more information, see the Codex MCP documentation.

---

Copilot CLI

Use the Copilot CLI to interactively add the MCPBrowser MCP server:

/mcp add

When prompted, enter the following values:

| Command | `npx -y mcpbrowser@lates