pulsemcp verified Safe content atomic mcp-remote

Chrome DevTools

This Chrome DevTools Protocol MCP server by Benjamin Rowell provides AI assistants with direct access to Chrome browser debugging capabilities through WebSocket connections to Chrome's remote debugging interface. Built in Python with comprehensive error handling and real-time event processing, it enables browser automation, network request monitoring, DOM inspection, JavaScript execution, console log analysis, performance metrics collection, and storage management across web applications. The implementation maintains persistent connections to capture live browser data and supports headless Chrome operations, making it particularly useful for web development debugging, automated testing workflows, and performance analysis tasks where AI assistants need to interact with and analyze web applications in real-time.

Cognium trust score

90%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

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/benjaminr/chrome-devtools-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Chrome DevTools 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

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"