"chrome" matching MCP servers:

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.

Local MCP server for persistent Chrome automation with multi-profile support, enabling tab management, page inspection, element interaction, JavaScript evaluation, and screenshots while preserving login sessions across restarts.

An MCP server that lets LLM agents control all Chrome browser tabs via accessibility snapshots, element references, and a virtual cursor, supporting operations like click, type, navigate, screenshot, and video recording.

Enables MCP clients to directly operate your existing logged-in Chrome profiles, including cookies and extensions, without re-authentication or a headless browser. It provides tools for managing tabs, navigating, reading pages, clicking, typing, and launching profiles.

An MCP server that gives AI agents faithful control of real, logged-in Chrome profiles via a secure local bridge and extension, with exact multi-profile routing and no debug profiles or remote debugging ports.

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.

Enables agents to drive an existing Chrome window by creating tabs, taking snapshots, pressing keys, and filling form fields via native messaging without opening a new browser instance.

Enables MCP clients to control real Chrome tabs in existing profiles, supporting navigation, interaction, screenshots, and console/network inspection across multiple Chrome instances.

Enables browser automation through a persistent Chrome instance exposed via HTTP, including navigation, screenshots, clicks, typing, multi-tab and multi-profile management, proxy switching, login state export, and AI-driven task execution.

Enables MCP clients to drive a real Chromium browser for automation, including navigation, JavaScript execution, CDP commands, network capture, and multi-tab control.

Enables browser control through your existing signed-in Chrome profile, letting MCP clients like Claude Code manage tabs, navigate, inspect pages, and perform real user interactions via tool calls. Works with any model backend without needing Playwright or a fresh browser profile.

Enables any coding agent to use the user's existing Chrome profiles and logins to open tabs, read pages, fill forms, click through flows, and take screenshots.

Enables AI agents to dynamically provision headless browser environments and connect to them through a unified HTTP/SSE MCP endpoint with persistent storage and automatic health monitoring.

Lets local AI agents drive the Chrome browser a user already has open, including signed-in sessions, by listing tabs, reading page text and actionable elements, then clicking, filling, selecting, scrolling, navigating, and capturing viewport screenshots without exporting cookies. Runs as a dependency-free local stdio process over Native Messaging, with per-tab leases, automatic reconnection, and pause/write-action controls.

Enables AI clients to drive a chosen account's isolated Chrome instance through MCP tools, covering profile discovery and start/stop, navigation, clicking, form filling, text extraction, screenshots, and queued multi-step jobs with result polling, plus manual handover for logins and CAPTCHAs. Also supports session and storage-state export, profile backups, and human takeover/resume when a task needs verification.

Enables AI agents to drive real Google Chrome with stealth and captcha handling, using Patchright to avoid bot detection.

Enables ZCode to control a real Chrome browser, including tabs, navigation, page content, clicks, form filling, keyboard input, scrolling, screenshots, and JavaScript evaluation through a local MCP bridge.

Enables local opencode agents to control a live Chrome browser via MCP tools, including tab management, JavaScript execution, clicking, form filling, page reading, screenshots, and console log retrieval.

Enables Grok Build to attach to the user's active Chrome profile via MCP, leveraging the profile's tabs, cookies, and logins instead of launching an isolated browser.

Enables coding agents to control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis.