"chrome" matching MCP servers:

Enables OpenCode to control a real browser through a local extension bridge, supporting navigation, DOM reading, clicking, typing, form filling, scrolling, dragging, screenshots, and more.

Lets several AI clients drive one shared, signed-in Chrome at the same time, giving each session its own background tabs and tab group with per-tab leases so mutations queue while reads overlap. Exposes a full Chrome DevTools-style toolset plus Claude's 31-member browser toolset, along with an HTTP endpoint that turns Messages API tool_use blocks into tool_result blocks.

MCP server for interactive feedback collection via Chrome extension, enabling users to submit text, images, and page elements.

An MCP server that connects AI agents to a running Chrome tab via the Chrome DevTools Protocol (CDP), enabling runtime debugging and page inspection.

Rust-based MCP server that lets AI agents natively control and debug Chromium browsers via the Chrome DevTools Protocol (CDP). Single pre-compiled binary, installable with npx @raultov/chrome-debug-mcp, Homebrew or one shell command — no Rust toolchain.

Enables AI agents to attach to Chrome tabs, set breakpoints, inspect scope variables, evaluate expressions, and step through code using Chrome DevTools Protocol for runtime debugging.

Enables AI to interact with Chrome DevTools Protocol to inspect and debug live web pages, including DOM, styles, console logs, and network requests.

Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.

Enables AI coding agents to inspect and operate Chrome as a developer, including reading DevTools console/network data, evaluating JavaScript, and managing unpacked extensions during an edit-test-debug loop.

Enables browser automation and inspection by connecting to an already-running Chrome/Chromium over the DevTools protocol, with page-scoped routing so multiple clients can control separate tabs concurrently.

Lets coding agents control and inspect a live Chrome browser via the Model-Context-Protocol, providing advanced browser debugging, performance insights, and reliable automation.

Enables MCP clients like Claude Desktop to automate and interact with claude.ai via a Chrome extension and WebSocket relay.

An MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.

Lets AI coding assistants control and inspect a live Chrome browser through MCP, enabling reliable automation, debugging, and performance analysis using Chrome DevTools.

Enables MCP clients to drive individually named Chrome profiles, providing tools for tabs, navigation, page interaction, screenshots, JavaScript evaluation, console logs, and network inspection over stdio without a TCP port.

Enables coding agents to control and inspect a live Chrome browser, providing reliable automation, debugging, performance insights, screenshots, network analysis, and console messages through MCP.

Enables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.

A token-optimized MCP server that groups Chrome Devtools tools into 8 semantic operations, reducing context window tokens by 69.5% while preserving full functionality.

Enables AI coding assistants to control and inspect a live Chrome browser through Chrome DevTools for automation, debugging, and performance analysis.

Enables AI coding agents to control and inspect a live Chrome browser for reliable automation, in-depth debugging, performance analysis, and high-speed batched or parallel workflows.