"Browser Tools for Managing MCP (Mission-Critical Processes)" matching MCP servers:

Persistence, headed Chromium browser control for MCP clients like OpenCode and Claude Code, enabling navigation, inspection, clicking, filling, and human-gated actions on JavaScript-heavy or login-walled pages.

Reliable, scalable browser infrastructure for AI agents. Route, pool, and failover across any browser provider. 8 built-in browser tools using raw Chrome CDP - navigate, screenshot, snapshot, interact, evaluate. Zero-config with auto Chrome detection & concurrent sessions support

Provides Dify apps with a secure, app-scoped MCP tool catalog and action gateway for authorized FlowFlox operations, enabling intent-driven planning and fixed operational processes without exposing global credentials.

Browser use using Typesafe's Jev model

Enables MCP clients to drive a self-hosted Chrome session for browsing tasks through browser tools, while providing a live view URL so a human can take over at prompts like logins or 2FA.

Trust Graduation gate for AI agents: visible approval ceremonies and receipt-backed boundaries for consequential actions.

MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.

It enables a single stdio MCP endpoint to multiplex calls by session_id to dedicated, isolated @playwright/mcp child processes, giving each session or subagent its own separate Chrome browser with isolated profiles and cookies.

MCP server for managing and controlling multiple isolated Chrome/Edge browser instances, exposing tools for navigation, screenshots, clicking, form filling, and JavaScript execution to AI clients.

Enables AI agents to control a Playwright-driven browser through natural-language instructions, including page interaction and live browser task execution.

Enables AI agents to drive a live, persistent self-hosted Chromium session over MCP, running browser actions via Playwright/CDP, capturing page snapshots, screenshots and videos, and managing uploads and downloads in the same tabs and signed-in accounts a human user can take over at any time.

Enables agents to control a visible Chromium browser via Playwright with tools for tabs, page reading, element finding, form input, mouse/keyboard actions, screenshots, console/network inspection, JavaScript execution, viewport emulation, and batched calls.

Fast Browser is an MCP server that lets Claude Code and Codex drive an existing Chrome browser with your real profile, logins, and tabs, using a macro library for multi-step flows in single tool calls and supporting concurrent agents with isolated tab groups.

Exposes browser tabs to any MCP client through a local broker, letting agents discover pages, take text snapshots with numbered elements, and drive them via click, type, navigate, eval, network/log inspection, and screenshots. Supports stdio, Streamable HTTP, and SSE transports so IDE and CLI agents can orchestrate browser automation.

A MCP server that allows AI assistants to interact with the browser, including getting page content as markdown, modifying page styles, and searching browser history.

Lets AI agents drive your real, already-logged-in browsers on macOS in the background without stealing focus, organizing work into tab groups, reading pages as compact accessibility snapshots, and saving repeatable scenarios. Supports Chrome, Edge, Brave, Yandex Browser, and Safari, with per-agent isolation and automatic tab cleanup.

Enables AI agents to open, read, and act on live web pages through verified browser actions, including filling forms, extracting data, debugging pages, and handling bot walls.

Enables MCP clients to drive a sandboxed Chromium container over CDP with tools for navigation, clicking, typing, selecting, key presses, scrolling, finding, text extraction, snapshots, and screenshots, optionally restricted by a host allowlist.

Lets OpenCode check whether Arc is open on Windows and navigate it to absolute HTTP(S) URLs from WSL2, even when another browser is the Windows default.

Enables AI assistants to browse the web efficiently via compact goal-based views, lazy image loading, and low-latency interactions.

An MCP server that gives an agent a remote browser:

MCP server providing browser automation for AI agents, enabling actions like clicking and typing, structured data extraction, content validation, multi-step task execution, and memory enrichment from web pages.

Use your existing Firefox and logged-in tabs, limited to tabs or tab groups you explicitly share.

Human-in-the-loop automation framework. Log them in, watch them run.

Enables AI assistants to control a web browser through Playwright-compatible tools, with an on-device decision engine for autonomous task completion and optional LLM escalation.

Lets MCP agents drive VS Code's integrated browser tab that the user shares with them: opening pages, taking accessibility snapshots and screenshots, clicking, typing, scrolling, dragging and reading console and network activity with real trusted input. It also maps a picked element back to the source file, line and column that rendered it, so an agent receives the same selection the developer clicked.

Enables Grok CLI to control your already-running Brave browser via Chrome DevTools Protocol, allowing tab management, clicking, typing, navigation, and screenshots using your existing session and logins.

Enables coding agents to drive a real, indexed Chrome browser over MCP stdio, navigating pages, observing numbered interactive elements, and performing click, type, and select actions without the server itself calling any model.

Lets any number of concurrent Claude Code sessions drive a Firefox browser through the Browser Control extension by funneling every session's commands over a single shared port via a background daemon and private unix socket. Sessions no longer have to compete for a limited pool of extension ports, and requests stay isolated through per-request correlation ids.

Exposes a headful, collaborative browser over MCP so an agent and a user can share one visible Chromium window: the agent navigates, reads, clicks, types, and fills forms, while the user watches and can take over for passwords, CAPTCHAs, 2FA, and payments, with every action written to an append-only audit trail. It also runs headless under a chat-based harness.