Chrome DevTools for coding agents

Open-source browser automation MCP server. Control your real Chrome from any AI agent.

Let Claude Code, Codex and any AI agent use the Chrome you're already signed in to. Open-source CLI + MCP server + Chrome extension (native messaging, no debug port); stealth by default.

Enables MCP clients to operate an already-logged-in Chrome tab through a browser extension and chrome.debugger, exposing navigation, page reading, interaction, screenshots, cookies/storage, network and console debugging, downloads, and batch actions under default-deny safety guards.

Extract any website's complete design system with one command. DTCG tokens, semantic+primitive+composite, MCP server for Claude Code/Cursor/Windsurf, multi-platform emitters (iOS SwiftUI, Android Compose, Flutter, WordPress), Tailwind v4, Figma variables, shadcn/ui, CSS health audit, WCAG remediation, Chrome extension. MIT, Playwright, Node 20+.

AI Agent-first JS 逆向 MCP Server：有头 Chrome 调试、断点、网络/WebSocket 分析、Patchright 反检测，可选 CloakBrowser。

Stealth browser automation for AI agents over MCP and the Chrome DevTools Protocol: navigation, network hooks, DOM extraction, and pixel-accurate UI cloning.

Browser MCP - the browser tool that can stop and ask you. A 2FA code, a CAPTCHA, a choice only you can make: it asks on your own screen, then carries on in the Chrome you're signed into. 40 tools, any MCP client, MIT.

177 tools for AI agents. Turn Chrome into an MCP server — inspect DOM, automate clicks, audit security, mock APIs, extract data, download videos, schedule agents, monitor pages, self-improving recipes, full API collection management, business intelligence

A search-first, profile-aware reverse-engineering workspace for AI agents — 735 tools across 36 domains in one MCP server.

Browser automation clicks buttons. OpenTabs calls APIs.

Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.

Enables MCP-capable agent CLIs on macOS to reuse an installed, unmodified OpenAI Browser Runtime to drive a connected Chrome or Edge browser (or a host's in-app browser backend) through js, js_reset, and turn_ended tools. It stays a thin bridge that preserves the Runtime's approval and security boundaries, failing closed when the client cannot handle approval requests.

Enables Claude or any MCP client to use the Google Gemini web app through a real Chrome browser with a normal Google account and no API key, including sending prompts, managing chats, uploading files, downloading results, and inspecting or interacting with pages via accessibility roles.

Enables agents and CLI users to drive their locally installed Google Chrome through a dedicated persistent profile over the DevTools Protocol, so they can navigate open HTTP/HTTPS sites, manage tabs, and inspect pages while keeping existing sign-ins and cookies.