Chrome Debug Protocol
Provides browser automation capabilities through Chrome's debugging protocol with session persistence, enabling web s...
What it does
Provides browser automation capabilities through Chrome's debugging protocol with session persistence, enabling web scraping, testing, and automation tasks with tools for screenshots, navigation, element interaction, and content retrieval.
This MCP server provides browser automation capabilities through Chrome's debugging protocol with session persistence, enabling AI agents to control Chrome instances for web scraping, testing, and automation tasks. Built using TypeScript with puppeteer-core and the Model Context Protocol SDK, it offers tools for taking screenshots in multiple formats (PNG, JPEG, WebP), navigating to URLs, clicking elements, typing text, and retrieving page content while maintaining browser sessions across multiple interactions. The implementation features automatic browser discovery, connection management with configurable debugging ports, error handling with detailed responses, and support for both headless and headed Chrome instances, making it valuable for automated testing workflows, web data extraction, and building AI assistants that need persistent browser control without manual Chrome DevTools access.
Capabilities
Server
Quality
deterministic score 0.62 from registry signals: · indexed on pulsemcp · has source repo · 9 github stars · registry-generated description present