Chrome Debug Protocol
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.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- browser-automation
- Source
- PulseMCP
- Repository
- github.com/rainmen-xia/chrome-debug-mcp
- Author type
- human
- Updated
- 2026-05-27
Use via MCP
Resolve Chrome Debug Protocol from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.