"A query about Google Chrome or a related Chrome topic" matching MCP servers:

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

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.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Enables Google search and webpage content extraction via Chrome for macOS, allowing access to both unauthenticated and authenticated content, and integrates with Claude for secure and automated browsing tasks.

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.

Enables AI agents to perform real Google web searches and render web pages for content extraction using a local Chrome browser, with human-in-the-loop CAPTCHA verification, requiring no API keys.

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

Enables AI coding agents to manage Chrome bookmarks and tab groups through MCP, using a sleep-by-default extension that wakes only when tools are called.

Enables browser automation via Chrome, allowing navigation, clicking, typing, screenshotting, and replayable flows for web tasks.

Drive your real, signed-in Chrome browser from any MCP client, enabling browser automation such as navigation, clicking, typing, and screenshots through standard MCP tools.

Enables fast Chrome browser automation over the DevTools Protocol, letting agents manage tabs, navigate pages, click, type, fill forms, take screenshots, and evaluate JavaScript. It runs via stdio or HTTP/SSE and can auto-launch Chrome with a persistent profile when needed.

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

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 controlling a local Chrome browser via MCP tools, using a Chrome extension and WebSocket broker for browser automation.

A local MCP server that enables Codex to inspect and interact with Chrome tabs through the Chrome DevTools Protocol, primarily for collecting authorized Brightspace course materials into local folders.

Bridges AI agents (Codex, Claude Code) with a real Chrome session via CDP, enabling Google Search and Google AI interactions through the browser.

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.

A Chrome extension-based Model Context Protocol server that enables AI assistants to control your browser, leveraging your existing configurations and login states for complex automation, content analysis, and semantic search.

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

A browser extension that turns Chrome into an AI-controlled automation tool, allowing AI assistants like Claude to control your browser, leverage existing login states, and perform complex tasks through a Model Context Protocol server.

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.

A Model Context Protocol server that enables AI assistants to control Chrome browsers through the Chrome DevTools Protocol, allowing for navigation, clicking, typing, and extracting page information.

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.

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.