"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.

Enables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.

Enables AI agents and CLI tools to dispatch downloads through Chrome's native download engine over the MCP protocol, automatically inheriting browser cookies, login sessions, and proxy settings. Supports submitting, monitoring, pausing, resuming, and cancelling download tasks locally without manual server setup.

MCP server + Chrome extension that drive the user's real, logged-in Chrome over a local WebSocket. 59 token-efficient web-dev tools: compact element refs instead of screenshots, server-side table filtering, visual regression, accessibility/SEO/security audits, network mocking. Also runs on ChromeOS/Crostini.

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 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.

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.

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.

Exposes a live Chrome browser to any MCP client through a single local endpoint, enabling real-tab control, DOM interaction, cookies and session use, network/console capture, PDF export, and CDP-powered debugging.

Enables MCP clients to drive your real Chrome profile through a local, token-protected bridge, so agents can open and navigate tabs, read page snapshots, click, type, scroll, wait, run JavaScript, and take screenshots while keeping your existing logins and extensions. It runs inside the Chrome you already use rather than a separate clean profile.

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.

Enables any MCP-capable AI agent to operate the user's own everyday Chrome browser with all existing login sessions intact, offering 22 tools for reading page/network data, filling forms, clicking, batch multi-step actions, and handing CAPTCHAs or confirmations back to the human — without API keys, debug ports, or launch flags.

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 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.

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.

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

Enables any MCP-compatible AI agent to drive your own Chrome browser with your existing login state, filling forms, clicking elements, fetching data, and handling captchas without API keys or re-authentication.