Chrome Debug Protocol
Rank #15559pulsemcp/chrome-debug
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.
Chrome Debug Protocol is a Model Context Protocol (MCP) server published by rainmen-xia. It ranks #15559 of 58,832 servers tracked on MCP Toplist, and its repository has 9 GitHub stars. Chrome Debug Protocol is listed on PulseMCP, and ships as a single rolling release with no explicit version metadata. It was first listed on Jun 30, 2025.
Ranks ahead of 43,273 of 58,832 servers on MCP Toplist.
Use Chrome Debug Protocol
Chrome Debug Protocol doesn’t publish a machine-readable install config. Follow the setup instructions in its repository ↗, or open one of its registry listings above.
Listed on 1 registry
rainmen-xia
Not versioned
This server is published through a registry that does not expose explicit version metadata. The listing tracks a single rolling release.
Frequently asked questions
- What is Chrome Debug Protocol?
- 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.
- Who maintains Chrome Debug Protocol?
- Chrome Debug Protocol is maintained by rainmen-xia, which publishes 1 MCP server (0 total versions) tracked on MCP Toplist.
- Is Chrome Debug Protocol an official MCP server?
- Chrome Debug Protocol is not on the Official MCP Registry. It is listed on PulseMCP.
- How many versions does Chrome Debug Protocol have?
- Chrome Debug Protocol ships as a single rolling release with no explicit version metadata.
- Where can I find the source code for Chrome Debug Protocol?
- The source code for Chrome Debug Protocol is hosted at github.com/rainmen-xia/chrome-debug-mcp.