Chrome Tools
This MCP server implementation provides tools for interacting with Chrome through its DevTools Protocol. Developed by nicholmikey, it enables remote control of Chrome tabs, including executing JavaScript, capturing screenshots, monitoring network traffic, and more. The server is designed to work in various environments, including native setups, WSL, and Docker, with configurable options for different use cases. It's particularly useful for scenarios where manual browser configuration is needed before AI interaction, or for capturing network events into an AI tool's context. The implementation focuses on flexibility and ease of use, offering a range of features from basic tab navigation to detailed DOM element querying and interaction.
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-19.
Scan details: Circle-IR · 2026-09-19 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- cloud-infra
- Source
- PulseMCP
- Repository
- github.com/nicholmikey/chrome-tools-mcp
- Author type
- human
- Last scanned
- 2026-09-19
- Updated
- 2026-09-19
Use via MCP
Resolve Chrome Tools 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.