"Google Chrome Browser Information or Downloads" matching MCP servers:

Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.

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 coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.

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

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

A fork of Chrome DevTools MCP that adds Streamable HTTP transport for multiple AI agents to concurrently control and inspect a live Chrome browser via the Model Context Protocol.

Enables AI assistants to control headless Chromium directly over the Chrome DevTools Protocol through nine MCP tools, covering navigation, text extraction, screenshots, console capture, accessibility snapshots, clicking, typing, waiting, and scrolling. It runs without Puppeteer or Playwright and is built for ARM64 and resource-constrained environments, with lazy browser launch and idle shutdown.

Lets coding agents control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis. Provides access to Chrome DevTools capabilities such as tracing, network inspection, screenshots, and console messages through MCP clients.

Enables any MCP client to drive the user's real Chrome profile through a Chrome extension bridge, with tools for navigation, accessibility snapshots, ref-based interactions, console/network reading, screenshots, tab management, and restricted script evaluation.

Lets coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.

MCP-ORTools integrates Google's OR-Tools constraint programming solver with Large Language Models through the MCP, enabling AI models to: Submit and validate constraint models Set model parameters Solve constraint satisfaction and optimization problems Retrieve and analyze solution

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

Enables AI coding agents to control and inspect a live Chrome browser via MCP, including performance tracing, network and console debugging, screenshots, and reliable Puppeteer-based automation.

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

MCP server + Chrome extension that gives AI coding agents control of your real browser with existing sessions, logins, and cookies. Works with Cursor, Claude, Windsurf.

Enables multiple MCP clients to share a single Chrome instance while maintaining isolated tab sessions for each client. It acts as a multiplexer between clients and the chrome-devtools-mcp server, preventing tab conflicts across different sessions like Claude Code windows.

A CDP-native MCP server that lets AI agents drive a real Chrome browser with deep network/console inspection, robust page interaction, and the ability to reverse-engineer a site's API flow into runnable code with dependency chaining and replay verification.

Lets an AI assistant inspect a running Google Chrome or Microsoft Edge browser over the Chrome DevTools Protocol, reading console output, network traffic, DOM snapshots, errors, performance metrics, storage, and screenshots. It also supports live event subscriptions, screen-frame streaming, and one-shot export of everything into an offline-readable archive such as HAR, CSV, and a self-contained HTML report.