Browser Automation MCP Servers

Connects AI assistants to the browser through a WebSocket-connected browser extension.

MCP server for browser control, tab management, and automation (currently Chrome-based)

MCP server for browser DevTools and backend debugging - analyze console logs, network requests, and backend logs with AI assistance

Playwright Tools for MCP

BrowserOxide — stealth headless browser engine in Rust (Python bindings) — real HTML/CSS/DOM/JS, own BoringSSL TLS, native fingerprint, no

BAP MCP Integration - Use Browser Agent Protocol as an MCP server

MCP server for browser automation with Set of Marks (SoM) - AI agents can see and interact with web pages using numbered element IDs

MCP server for browser automation using Browser MCP

MCP server for driving a local camofox-browser instance.

Stdio MCP server for the camofox-browser HTTP API

MCP server for browser automation using Camoufox - a privacy-focused Firefox fork with advanced anti-detection features

MCP server that bridges clients to a real browser through CDP and a companion extension.

A lightweight chrome-devtools-mcp alternative: a single-target Chrome DevTools Protocol MCP server + CLI that drives one tab over a direct

Connects AI assistants to the Chrome DevTools Protocol for runtime debugging, including breakpoints, variable inspection, network

MCP browser server - fetch web pages using real Chrome/Edge/Brave browser. Handles authentication, SSO, CAPTCHAs, and anti-bot protection

MCP server for Chrome — multi-tab parallel control, DevTools inspection, browser management

MCP server for browser automation with custom scripts

Chrome Native-Messaging host (Node)

Chrome Native-Messaging host (Node) - Fork with Chrome Web Store support

Local MCP server and Chrome MV3 extension for controlling the current Chrome profile from any stdio MCP host.

MCP server for capturing Chrome console logs via CDP